Method and apparatus for configuring a-ppdu in wireless lan system

ABSTRACT

Proposed are a method and apparatus for configuring an A-PPDU in a wireless LAN system. Specifically, a reception STA receives an A-PPDU from a transmission STA and decodes the A-PPDU. The A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel. The first PPDU includes a first indicator including information about a bandwidth of the first PPDU. The second PPDU includes a second indicator including information about a bandwidth of the second PPDU. The first PPDU is a PPDU that supports an HE wireless LAN system, and the second PPDU is a PPDU that supports an EHT wireless LAN system.

TECHNICAL FIELD

The present specification relates to a technique for receiving an A-PPDU in a WLAN system, and more particularly, to a method and apparatus for configuring an A-PPDU capable of simultaneously transmitting an HE PPDU and an EHT PPDU.

BACKGROUND

A wireless local area network (WLAN) has been enhanced in various ways. For example, the IEEE 802.11ax standard has proposed an enhanced communication environment by using orthogonal frequency division multiple access (OFDMA) and downlink multi-user multiple input multiple output (DL MU MIMO) schemes.

The present specification proposes a technical feature that can be utilized in a new communication standard. For example, the new communication standard may be an extreme high throughput (EHT) standard which is currently being discussed. The EHT standard may use an increased bandwidth, an enhanced PHY layer protocol data unit (PPDU) structure, an enhanced sequence, a hybrid automatic repeat request (HARQ) scheme, or the like, which is newly proposed. The EHT standard may be called the IEEE 802.11be standard.

An increased number of spatial streams may be used in the new wireless LAN standard. In this case, in order to properly use the increased number of spatial streams, a signaling technique in the WLAN system may need to be improved.

SUMMARY

The present specification proposes a method and apparatus for configuring an A-PPDU in a WLAN system.

An example of the present specification proposes a method for receiving an A-PPDU.

The present embodiment may be performed in a network environment in which a next-generation wireless LAN system (IEEE 802.11be or EHT wireless LAN system) is supported. The next-generation wireless LAN system may be a wireless LAN system improved from the 802.11ax system, and may satisfy backward compatibility with the 802.11ax system.

This embodiment proposes a method of configuring an A-PPDU in which an HE PPDU and an EHT PPDU are simultaneously transmitted. In addition, this embodiment proposes a method of indicating the bandwidth of each sub-PPDU in the A-PPDU and a method of setting an STF/LTF sequence in each sub-PPDU.

A receiving station (STA) receives an Aggregated-Physical Protocol Data Unit (A-PPDU) from a transmitting STA.

The receiving STA decodes the A-PPDU.

The A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel. The first PPDU is a PPDU supporting a High Efficiency (HE) WLAN system, and the second PPDU is a PPDU supporting an Extremely High Throughput (EHT) WLAN system. That is, the HE PPDU and the EHT PPDU may be aggregated with each other in the frequency domain and transmitted simultaneously through the A-PPDU. Since the bandwidth that the HE WLAN system can support is 160 MHz, it is preferable that the HE PPDU is configured in the primary 160 MHz channel and the EHT PPDU is configured in the secondary 160 MHz channel.

The first PPDU includes a first indicator including information on the bandwidth of the first PPDU. The second PPDU includes a second indicator including information on the bandwidth of the second PPDU.

According to the embodiment proposed in the present specification, by configuring an A-PPDU capable of transmitting both the HE PPDU and the EHT PPDU at the same time, there is an effect that PPDU transmission/reception between the HE STA and the EHT STA can be efficiently supported.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a transmitting apparatus and/or receiving apparatus of the present specification.

FIG. 2 is a conceptual view illustrating the structure of a wireless local area network (WLAN).

FIG. 3 illustrates a general link setup process.

FIG. 4 illustrates an example of a PPDU used in an IEEE standard.

FIG. 5 illustrates a layout of resource units (RUs) used in a band of 20 MHz.

FIG. 6 illustrates a layout of RUs used in a band of 40 MHz.

FIG. 7 illustrates a layout of RUs used in a band of 80 MHz.

FIG. 8 illustrates a structure of an HE-SIG-B field.

FIG. 9 illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme.

FIG. 10 illustrates an example of a PPDU used in the present specification.

FIG. 11 illustrates an example of a modified transmission device and/or receiving device of the present specification.

FIG. 12 is a diagram of a representative Aggregated PPDU.

FIG. 13 shows an example of the structure of U-SIG.

FIG. 14 is a flowchart illustrating the operation of the transmitting apparatus/device according to the present embodiment.

FIG. 15 is a flowchart illustrating the operation of the receiving apparatus/device according to the present embodiment.

FIG. 16 is a flowchart illustrating a procedure in which a transmitting STA transmits an A-PPDU according to the present embodiment.

FIG. 17 is a flowchart illustrating a procedure in which a receiving STA receives an A-PPDU according to the present embodiment.

DETAILED DESCRIPTION

In the present specification, “A or B” may mean “only A”, “only B” or “both A and B”. In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in the present specification, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”.

A slash (/) or comma used in the present specification may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.

In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”.

In addition, in the present specification, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”.

In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (EHT-signal)”, it may denote that “EHT-signal” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “EHT-signal”, and “EHT-signal” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., EHT-signal)”, it may also mean that “EHT-signal” is proposed as an example of the “control information”.

Technical features described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.

The following example of the present specification may be applied to various wireless communication systems. For example, the following example of the present specification may be applied to a wireless local area network (WLAN) system. For example, the present specification may be applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11ax standard. In addition, the present specification may also be applied to the newly proposed EHT standard or IEEE 802.11be standard. In addition, the example of the present specification may also be applied to a new WLAN standard enhanced from the EHT standard or the IEEE 802.11be standard. In addition, the example of the present specification may be applied to a mobile communication system. For example, it may be applied to a mobile communication system based on long term evolution (LTE) depending on a 3^(rd) generation partnership project (3GPP) standard and based on evolution of the LTE. In addition, the example of the present specification may be applied to a communication system of a 5G NR standard based on the 3GPP standard.

Hereinafter, in order to describe a technical feature of the present specification, a technical feature applicable to the present specification will be described.

FIG. 1 shows an example of a transmitting apparatus and/or receiving apparatus of the present specification.

In the example of FIG. 1 , various technical features described below may be performed. FIG. 1 relates to at least one station (STA). For example, STAs 110 and 120 of the present specification may also be called in various terms such as a mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, or simply a user. The STAs 110 and 120 of the present specification may also be called in various terms such as a network, a base station, a node-B, an access point (AP), a repeater, a router, a relay, or the like. The STAs 110 and 120 of the present specification may also be referred to as various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, or the like.

For example, the STAs 110 and 120 may serve as an AP or a non-AP. That is, the STAs 110 and 120 of the present specification may serve as the AP and/or the non-AP.

The STAs 110 and 120 of the present specification may support various communication standards together in addition to the IEEE 802.11 standard. For example, a communication standard (e.g., LTE, LTE-A, 5G NR standard) or the like based on the 3GPP standard may be supported. In addition, the STA of the present specification may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, or the like. In addition, the STA of the present specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving (autonomous-driving), or the like.

The STAs 110 and 120 of the present specification may include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a radio medium.

The STAs 110 and 120 will be described below with reference to a sub-figure (a) of FIG. 1 .

The first STA 110 may include a processor 111, a memory 112, and a transceiver 113. The illustrated process, memory, and transceiver may be implemented individually as separate chips, or at least two blocks/functions may be implemented through a single chip.

The transceiver 113 of the first STA performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received.

For example, the first STA 110 may perform an operation intended by an AP. For example, the processor 111 of the AP may receive a signal through the transceiver 113, process a reception (RX) signal, generate a transmission (TX) signal, and provide control for signal transmission. The memory 112 of the AP may store a signal (e.g., RX signal) received through the transceiver 113, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.

For example, the second STA 120 may perform an operation intended by a non-AP STA. For example, a transceiver 123 of a non-AP performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be packet, etc.) may be transmitted/received.

For example, a processor 121 of the non-AP STA may receive a signal through the transceiver 123, process an RX signal, generate a TX signal, and provide control for signal transmission. A memory 122 of the non-AP STA may store a signal (e.g., RX signal) received through the transceiver 123, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.

For example, an operation of a device indicated as an AP in the specification described below may be performed in the first STA 110 or the second STA 120. For example, if the first STA 110 is the AP, the operation of the device indicated as the AP may be controlled by the processor 111 of the first STA 110, and a related signal may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory 112 of the first STA 110. In addition, if the second STA 120 is the AP, the operation of the device indicated as the AP may be controlled by the processor 121 of the second STA 120, and a related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory 122 of the second STA 120.

For example, in the specification described below, an operation of a device indicated as a non-AP (or user-STA) may be performed in the first STA 110 or the second STA 120. For example, if the second STA 120 is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 121 of the second STA 120, and a related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory 122 of the second STA 120. For example, if the first STA 110 is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 111 of the first STA 110, and a related signal may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory 112 of the first STA 110.

In the specification described below, a device called a (transmitting/receiving) STA, a first STA, a second STA, a STA1, a STA2, an AP, a first AP, a second AP, an AP1, an AP2, a (transmitting/receiving) terminal, a (transmitting/receiving) device, a (transmitting/receiving) apparatus, a network, or the like may imply the STAs 110 and 120 of FIG. 1 . For example, a device indicated as, without a specific reference numeral, the (transmitting/receiving) STA, the first STA, the second STA, the STA1, the STA2, the AP, the first AP, the second AP, the AP1, the AP2, the (transmitting/receiving) terminal, the (transmitting/receiving) device, the (transmitting/receiving) apparatus, the network, or the like may imply the STAs 110 and 120 of FIG. 1 . For example, in the following example, an operation in which various STAs transmit/receive a signal (e.g., a PPDU) may be performed in the transceivers 113 and 123 of FIG. 1 . In addition, in the following example, an operation in which various STAs generate a TX/RX signal or perform data processing and computation in advance for the TX/RX signal may be performed in the processors 111 and 121 of FIG. 1 . For example, an example of an operation for generating the TX/RX signal or performing the data processing and computation in advance may include: 1) an operation of determining/obtaining/configuring/computing/decoding/encoding bit information of a sub-field (SIG, STF, LTF, Data) included in a PPDU; 2) an operation of determining/configuring/obtaining a time resource or frequency resource (e.g., a subcarrier resource) or the like used for the sub-field (SIG, STF, LTF, Data) included the PPDU; 3) an operation of determining/configuring/obtaining a specific sequence (e.g., a pilot sequence, an STF/LTF sequence, an extra sequence applied to SIG) or the like used for the sub-field (SIG, STF, LTF, Data) field included in the PPDU; 4) a power control operation and/or power saving operation applied for the STA; and 5) an operation related to determining/obtaining/configuring/decoding/encoding or the like of an ACK signal. In addition, in the following example, a variety of information used by various STAs for determining/obtaining/configuring/computing/decoding/decoding a TX/RX signal (e.g., information related to a field/subfield/control field/parameter/power or the like) may be stored in the memories 112 and 122 of FIG. 1 .

The aforementioned device/STA of the sub-figure (a) of FIG. 1 may be modified as shown in the sub-figure (b) of FIG. 1 . Hereinafter, the STAs 110 and 120 of the present specification will be described based on the sub-figure (b) of FIG. 1 .

For example, the transceivers 113 and 123 illustrated in the sub-figure (b) of FIG. 1 may perform the same function as the aforementioned transceiver illustrated in the sub-figure (a) of FIG. 1 . For example, processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1 may include the processors 111 and 121 and the memories 112 and 122. The processors 111 and 121 and memories 112 and 122 illustrated in the sub-figure (b) of FIG. 1 may perform the same function as the aforementioned processors 111 and 121 and memories 112 and 122 illustrated in the sub-figure (a) of FIG. 1 .

A mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, a user, a user STA, a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, a receiving unit, a transmitting unit, a receiving STA, a transmitting STA, a receiving device, a transmitting device, a receiving apparatus, and/or a transmitting apparatus, which are described below, may imply the STAs 110 and 120 illustrated in the sub-figure (a)/(b) of FIG. 1 , or may imply the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1 . That is, a technical feature of the present specification may be performed in the STAs 110 and 120 illustrated in the sub-figure (a)/(b) of FIG. 1 , or may be performed only in the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1 . For example, a technical feature in which the transmitting STA transmits a control signal may be understood as a technical feature in which a control signal generated in the processors 111 and 121 illustrated in the sub-figure (a)/(b) of FIG. 1 is transmitted through the transceivers 113 and 123 illustrated in the sub-figure (a)/(b) of FIG. 1 . Alternatively, the technical feature in which the transmitting STA transmits the control signal may be understood as a technical feature in which the control signal to be transferred to the transceivers 113 and 123 is generated in the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1 .

For example, a technical feature in which the receiving STA receives the control signal may be understood as a technical feature in which the control signal is received by means of the transceivers 113 and 123 illustrated in the sub-figure (a) of FIG. 1 . Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers 113 and 123 illustrated in the sub-figure (a) of FIG. 1 is obtained by the processors 111 and 121 illustrated in the sub-figure (a) of FIG. 1 . Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers 113 and 123 illustrated in the sub-figure (b) of FIG. 1 is obtained by the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1 .

Referring to the sub-figure (b) of FIG. 1 , software codes 115 and 125 may be included in the memories 112 and 122. The software codes 115 and 126 may include instructions for controlling an operation of the processors 111 and 121. The software codes 115 and 125 may be included as various programming languages.

The processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, a logic circuit and/or a data processing device. The processor may be an application processor (AP). For example, the processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, the processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may be SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or processors enhanced from these processors.

In the present specification, an uplink may imply a link for communication from a non-AP STA to an SP STA, and an uplink PPDU/packet/signal or the like may be transmitted through the uplink. In addition, in the present specification, a downlink may imply a link for communication from the AP STA to the non-AP STA, and a downlink PPDU/packet/signal or the like may be transmitted through the downlink.

FIG. 2 is a conceptual view illustrating the structure of a wireless local area network (WLAN).

An upper part of FIG. 2 illustrates the structure of an infrastructure basic service set (BSS) of institute of electrical and electronic engineers (IEEE) 802.11.

Referring the upper part of FIG. 2 , the wireless LAN system may include one or more infrastructure BSSs 200 and 205 (hereinafter, referred to as BSS). The BSSs 200 and 205 as a set of an AP and a STA such as an access point (AP) 225 and a station (STA1) 200-1 which are successfully synchronized to communicate with each other are not concepts indicating a specific region. The BSS 205 may include one or more STAs 205-1 and 205-2 which may be joined to one AP 230.

The BSS may include at least one STA, APs providing a distribution service, and a distribution system (DS) 210 connecting multiple APs.

The distribution system 210 may implement an extended service set (ESS) 240 extended by connecting the multiple BSSs 200 and 205. The ESS 240 may be used as a term indicating one network configured by connecting one or more APs 225 or 230 through the distribution system 210. The AP included in one ESS 240 may have the same service set identification (SSID).

A portal 220 may serve as a bridge which connects the wireless LAN network (IEEE 802.11) and another network (e.g., 802.X).

In the BSS illustrated in the upper part of FIG. 2 , a network between the APs 225 and 230 and a network between the APs 225 and 230 and the STAs 200-1, 205-1, and 205-2 may be implemented. However, the network is configured even between the STAs without the APs 225 and 230 to perform communication. A network in which the communication is performed by configuring the network even between the STAs without the APs 225 and 230 is defined as an Ad-Hoc network or an independent basic service set (IBSS).

A lower part of FIG. 2 illustrates a conceptual view illustrating the IBSS.

Referring to the lower part of FIG. 2 , the IBSS is a BSS that operates in an Ad-Hoc mode. Since the IBSS does not include the access point (AP), a centralized management entity that performs a management function at the center does not exist. That is, in the IBSS, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed by a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 may be constituted by movable STAs and are not permitted to access the DS to constitute a self-contained network.

FIG. 3 illustrates a general link setup process.

In S310, a STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, to access a network, the STA needs to discover a participating network. The STA needs to identify a compatible network before participating in a wireless network, and a process of identifying a network present in a particular area is referred to as scanning. Scanning methods include active scanning and passive scanning.

FIG. 3 illustrates a network discovery operation including an active scanning process. In active scanning, a STA performing scanning transmits a probe request frame and waits for a response to the probe request frame in order to identify which AP is present around while moving to channels. A responder transmits a probe response frame as a response to the probe request frame to the STA having transmitted the probe request frame. Here, the responder may be a STA that transmits the last beacon frame in a BSS of a channel being scanned. In the BSS, since an AP transmits a beacon frame, the AP is the responder. In an IBSS, since STAs in the IBSS transmit a beacon frame in turns, the responder is not fixed. For example, when the STA transmits a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA may store BSS-related information included in the received probe response frame, may move to the next channel (e.g., channel 2), and may perform scanning (e.g., transmits a probe request and receives a probe response via channel 2) by the same method.

Although not shown in FIG. 3 , scanning may be performed by a passive scanning method. In passive scanning, a STA performing scanning may wait for a beacon frame while moving to channels. A beacon frame is one of management frames in IEEE 802.11 and is periodically transmitted to indicate the presence of a wireless network and to enable the STA performing scanning to find the wireless network and to participate in the wireless network. In a BSS, an AP serves to periodically transmit a beacon frame. In an IBSS, STAs in the IBSS transmit a beacon frame in turns. Upon receiving the beacon frame, the STA performing scanning stores information related to a BSS included in the beacon frame and records beacon frame information in each channel while moving to another channel. The STA having received the beacon frame may store BSS-related information included in the received beacon frame, may move to the next channel, and may perform scanning in the next channel by the same method.

After discovering the network, the STA may perform an authentication process in S320. The authentication process may be referred to as a first authentication process to be clearly distinguished from the following security setup operation in S340. The authentication process in S320 may include a process in which the STA transmits an authentication request frame to the AP and the AP transmits an authentication response frame to the STA in response. The authentication frames used for an authentication request/response are management frames.

The authentication frames may include information related to an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), and a finite cyclic group.

The STA may transmit the authentication request frame to the AP. The AP may determine whether to allow the authentication of the STA based on the information included in the received authentication request frame. The AP may provide the authentication processing result to the STA via the authentication response frame.

When the STA is successfully authenticated, the STA may perform an association process in S330. The association process includes a process in which the STA transmits an association request frame to the AP and the AP transmits an association response frame to the STA in response. The association request frame may include, for example, information related to various capabilities, a beacon listen interval, a service set identifier (SSID), a supported rate, a supported channel, RSN, a mobility domain, a supported operating class, a traffic indication map (TIM) broadcast request, and an interworking service capability. The association response frame may include, for example, information related to various capabilities, a status code, an association ID (AID), a supported rate, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise indicator (RSNI), a mobility domain, a timeout interval (association comeback time), an overlapping BSS scanning parameter, a TIM broadcast response, and a QoS map.

In S340, the STA may perform a security setup process. The security setup process in S340 may include a process of setting up a private key through four-way handshaking, for example, through an extensible authentication protocol over LAN (EAPOL) frame.

FIG. 4 illustrates an example of a PPDU used in an IEEE standard.

As illustrated, various types of PHY protocol data units (PPDUs) are used in IEEE a/g/n/ac standards. Specifically, an LTF and a STF include a training signal, a SIG-A and a SIG-B include control information for a receiving STA, and a data field includes user data corresponding to a PSDU (MAC PDU/aggregated MAC PDU).

FIG. 4 also includes an example of an HE PPDU according to IEEE 802.11ax. The HE PPDU according to FIG. 4 is an illustrative PPDU for multiple users. An HE-SIG-B may be included only in a PPDU for multiple users, and an HE-SIG-B may be omitted in a PPDU for a single user.

As illustrated in FIG. 4 , the HE-PPDU for multiple users (MUs) may include a legacy-short training field (L-STF), a legacy-long training field (L-LTF), a legacy-signal (L-SIG), a high efficiency-signal A (HE-SIG A), a high efficiency-signal-B (HE-SIG B), a high efficiency-short training field (HE-STF), a high efficiency-long training field (HE-LTF), a data field (alternatively, an MAC payload), and a packet extension (PE) field. The respective fields may be transmitted for illustrated time periods (i.e., 4 or 8 μs).

Hereinafter, a resource unit (RU) used for a PPDU is described. An RU may include a plurality of subcarriers (or tones). An RU may be used to transmit a signal to a plurality of STAs according to OFDMA. Further, an RU may also be defined to transmit a signal to one STA. An RU may be used for an STF, an LTF, a data field, or the like.

FIG. 5 illustrates a layout of resource units (RUs) used in a band of 20 MHz.

As illustrated in FIG. 5 , resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to form some fields of an HE-PPDU. For example, resources may be allocated in illustrated RUs for an HE-STF, an HE-LTF, and a data field.

As illustrated in the uppermost part of FIG. 5 , a 26-unit (i.e., a unit corresponding to 26 tones) may be disposed. Six tones may be used for a guard band in the leftmost band of the 20 MHz band, and five tones may be used for a guard band in the rightmost band of the 20 MHz band. Further, seven DC tones may be inserted in a center band, that is, a DC band, and a 26-unit corresponding to 13 tones on each of the left and right sides of the DC band may be disposed. A 26-unit, a 52-unit, and a 106-unit may be allocated to other bands. Each unit may be allocated for a receiving STA, that is, a user.

The layout of the RUs in FIG. 5 may be used not only for a multiple users (MUs) but also for a single user (SU), in which case one 242-unit may be used and three DC tones may be inserted as illustrated in the lowermost part of FIG. 5 .

Although FIG. 5 proposes RUs having various sizes, that is, a 26-RU, a 52-RU, a 106-RU, and a 242-RU, specific sizes of RUs may be extended or increased. Therefore, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones).

FIG. 6 illustrates a layout of RUs used in a band of 40 MHz.

Similarly to FIG. 5 in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, and the like may be used in an example of FIG. 6 . Further, five DC tones may be inserted in a center frequency, 12 tones may be used for a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 40 MHz band.

As illustrated in FIG. 6 , when the layout of the RUs is used for a single user, a 484-RU may be used. The specific number of RUs may be changed similarly to FIG. 5 .

FIG. 7 illustrates a layout of RUs used in a band of 80 MHz.

Similarly to FIG. 5 and FIG. 6 in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, a 996-RU, and the like may be used in an example of FIG. 7 . Further, seven DC tones may be inserted in the center frequency, 12 tones may be used for a guard band in the leftmost band of the 80 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 80 MHz band. In addition, a 26-RU corresponding to 13 tones on each of the left and right sides of the DC band may be used.

As illustrated in FIG. 7 , when the layout of the RUs is used for a single user, a 996-RU may be used, in which case five DC tones may be inserted.

The RU described in the present specification may be used in uplink (UL) communication and downlink (DL) communication. For example, when UL-MU communication which is solicited by a trigger frame is performed, a transmitting STA (e.g., an AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA through the trigger frame, and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. Thereafter, the first STA may transmit a first trigger-based PPDU based on the first RU, and the second STA may transmit a second trigger-based PPDU based on the second RU. The first/second trigger-based PPDU is transmitted to the AP at the same (or overlapped) time period.

For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) may allocate the first RU (e.g., 26/52/106/242-RU. etc.) to the first STA, and may allocate the second RU (e.g., 26/52/106/242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit HE-STF, HE-LTF, and Data fields for the first STA through the first RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and Data fields for the second STA through the second RU.

Information related to a layout of the RU may be signaled through HE-SIG-B.

FIG. 8 illustrates a structure of an HE-SIG-B field.

As illustrated, an HE-SIG-B field 810 includes a common field 820 and a user-specific field 830. The common field 820 may include information commonly applied to all users (i.e., user STAs) which receive SIG-B. The user-specific field 830 may be called a user-specific control field. When the SIG-B is transferred to a plurality of users, the user-specific field 830 may be applied only any one of the plurality of users.

As illustrated in FIG. 8 , the common field 820 and the user-specific field 830 may be separately encoded.

The common field 820 may include RU allocation information of N*8 bits. For example, the RU allocation information may include information related to a location of an RU. For example, when a 20 MHz channel is used as shown in FIG. 5 , the RU allocation information may include information related to a specific frequency band to which a specific RU (26-RU/52-RU/106-RU) is arranged.

An example of a case in which the RU allocation information consists of 8 bits is as follows.

TABLE 1 RU Allocation subfield (B7 B6 B5 B4 Number B3 B2 B1 B0) #1 #2 #3 #4 #5 #6 #7 #8 #9 of entries 00000000 26 26 26 26 26 26 26 26 26 1 00000001 26 26 26 26 26 26 26 52 1 00000010 26 26 26 26 26 52 26 26 1 00000011 26 26 26 26 26 52 52 1 00000100 26 26 52 26 26 26 26 26 1 00000101 26 26 52 26 26 26 52 1 00000110 26 26 52 26 52 26 26 1 00000111 26 26 52 26 52 52 1 00001000 52 26 26 26 26 26 26 26 1 00001001 52 26 26 26 26 26 52 1 00001010 52 26 26 26 52 26 26 1

As shown the example of FIG. 5 , up to nine 26-RUs may be allocated to the 20 MHz channel. When the RU allocation information of the common field 820 is set to “00000000” as shown in Table 1, the nine 26-RUs may be allocated to a corresponding channel (i.e., 20 MHz). In addition, when the RU allocation information of the common field 820 is set to “00000001” as shown in Table 1, seven 26-RUs and one 52-RU are arranged in a corresponding channel. That is, in the example of FIG. 5 , the 52-RU may be allocated to the rightmost side, and the seven 26-RUs may be allocated to the left thereof.

The example of Table 1 shows only some of RU locations capable of displaying the RU allocation information.

For example, the RU allocation information may include an example of Table 2 below.

TABLE 2 8 bits indices (B7 B6 B5 B4 Number B3 B2 B1 B0) #1 #2 #3 #4 #5 #6 #7 #8 #9 of entries 01000y₂y₁y₀ 106 26 26 26 26 26 8 01001y₂y₁y₀ 106 26 26 26 52 8

“01000y2y1y0” relates to an example in which a 106-RU is allocated to the leftmost side of the 20 MHz channel, and five 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (e.g., user-STAs) may be allocated to the 106-RU, based on a MU-MIMO scheme. Specifically, up to 8 STAs (e.g., user-STAs) may be allocated to the 106-RU, and the number of STAs (e.g., user-STAs) allocated to the 106-RU is determined based on 3-bit information (y2y1y0). For example, when the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., user-STAs) allocated to the 106-RU based on the MU-MIMO scheme may be N+1.

In general, a plurality of STAs (e.g., user STAs) different from each other may be allocated to a plurality of RUs. However, the plurality of STAs (e.g., user STAs) may be allocated to one or more RUs having at least a specific size (e.g., 106 subcarriers), based on the MU-MIMO scheme.

As shown in FIG. 8 , the user-specific field 830 may include a plurality of user fields. As described above, the number of STAs (e.g., user STAs) allocated to a specific channel may be determined based on the RU allocation information of the common field 820. For example, when the RU allocation information of the common field 820 is “00000000”, one user STA may be allocated to each of nine 26-RUs (e.g., nine user STAs may be allocated). That is, up to 9 user STAs may be allocated to a specific channel through an OFDMA scheme. In other words, up to 9 user STAs may be allocated to a specific channel through a non-MU-MIMO scheme.

For example, when RU allocation is set to “01000y2y1y0”, a plurality of STAs may be allocated to the 106-RU arranged at the leftmost side through the MU-MIMO scheme, and five user STAs may be allocated to five 26-RUs arranged to the right side thereof through the non-MU MIMO scheme. This case is specified through an example of FIG. 9 .

FIG. 9 illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme.

For example, when RU allocation is set to “01000010” as shown in FIG. 9 , a 106-RU may be allocated to the leftmost side of a specific channel, and five 26-RUs may be allocated to the right side thereof. In addition, three user STAs may be allocated to the 106-RU through the MU-MIMO scheme. As a result, since eight user STAs are allocated, the user-specific field 830 of HE-SIG-B may include eight user fields.

The eight user fields may be expressed in the order shown in FIG. 9 . In addition, as shown in FIG. 8 , two user fields may be implemented with one user block field.

The user fields shown in FIG. 8 and FIG. 9 may be configured based on two formats. That is, a user field related to a MU-MIMO scheme may be configured in a first format, and a user field related to a non-MIMO scheme may be configured in a second format. Referring to the example of FIG. 9 , a user field 1 to a user field 3 may be based on the first format, and a user field 4 to a user field 8 may be based on the second format. The first format or the second format may include bit information of the same length (e.g., 21 bits).

Each user field may have the same size (e.g., 21 bits). For example, the user field of the first format (the first of the MU-MIMO scheme) may be configured as follows.

For example, a first bit (i.e., B0-B10) in the user field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of a user STA to which a corresponding user field is allocated. In addition, a second bit (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to a spatial configuration. Specifically, an example of the second bit (i.e., B11-B14) may be as shown in Table 3 and Table 4 below.

TABLE 3 N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) Total Number N_(user) B3 . . . B0 [1] [2] [3] [4] [5] [6] [7] [8] N_(STS) of entries 2 0000-0011 1-4 1 2-5 10 0100-0110 2-4 2 4-6 0111-1000 3-4 3 6-7 1001 4 4 8 3 0000-0011 1-4 1 1 3-6 13 0100-0110 2-4 2 1 5-7 0111-1000 3-4 3 1 7-8 1001-1011 2-4 2 2 6-8 1100 3 3 2 8 4 0000-0011 1-4 1 1 1 4-7 11 0100-0110 2-4 2 1 1 6-8 0111 3 3 1 1 8 1000-1001 2-3 2 2 1 7-8 1010 2 2 2 2 8

TABLE 4 N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) Total Number N_(user) B3 . . . B0 [1] [2] [3] [4] [5] [6] [7] [8] N_(STS) of entries 5 0000-0011 1-4 1 1 1 1 5-8 7 0100-0101 2-3 2 1 1 1 7-8 0110 2 2 2 1 1 8 6 0000-0010 1-3 1 1 1 1 1 6-8 4 0011 2 2 1 1 1 1 8 7 0000-0001 1-2 1 1 1 1 1 1 7-8 2 8 0000 1 1 1 1 1 1 1 1 8 1

As shown in Table 3 and/or Table 4, the second bit (e.g., B11-B14) may include information related to the number of spatial streams allocated to the plurality of user STAs which are allocated based on the MU-MIMO scheme. For example, when three user STAs are allocated to the 106-RU based on the MU-MIMO scheme as shown in FIG. 9 , N_user is set to “3”. Therefore, values of N_STS[1], N_STS[2], and N_STS[3] may be determined as shown in Table 3. For example, when a value of the second bit (B11-B14) is “0011”, it may be set to N_STS[1]=4, N_STS[2]=1, N_STS[3]=1. That is, in the example of FIG. 9 , four spatial streams may be allocated to the user field 1, one spatial stream may be allocated to the user field 1, and one spatial stream may be allocated to the user field 3.

As shown in the example of Table 3 and/or Table 4, information (i.e., the second bit, B11-B14) related to the number of spatial streams for the user STA may consist of 4 bits. In addition, the information (i.e., the second bit, B11-B14) on the number of spatial streams for the user STA may support up to eight spatial streams. In addition, the information (i.e., the second bit, B11-B14) on the number of spatial streams for the user STA may support up to four spatial streams for one user STA.

In addition, a third bit (i.e., B15-18) in the user field (i.e., 21 bits) may include modulation and coding scheme (MCS) information. The MCS information may be applied to a data field in a PPDU including corresponding SIG-B.

An MCS, MCS information, an MCS index, an MCS field, or the like used in the present specification may be indicated by an index value. For example, the MCS information may be indicated by an index 0 to an index 11. The MCS information may include information related to a constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information related to a coding rate (e.g., 1/2, 2/3, 3/4, 5/6e, etc.). Information related to a channel coding type (e.g., LCC or LDPC) may be excluded in the MCS information.

In addition, a fourth bit (i.e., B19) in the user field (i.e., 21 bits) may be a reserved field.

In addition, a fifth bit (i.e., B20) in the user field (i.e., 21 bits) may include information related to a coding type (e.g., BCC or LDPC). That is, the fifth bit (i.e., B20) may include information related to a type (e.g., BCC or LDPC) of channel coding applied to the data field in the PPDU including the corresponding SIG-B.

The aforementioned example relates to the user field of the first format (the format of the MU-MIMO scheme). An example of the user field of the second format (the format of the non-MU-MIMO scheme) is as follows.

A first bit (e.g., B0-B10) in the user field of the second format may include identification information of a user STA. In addition, a second bit (e.g., B11-B13) in the user field of the second format may include information related to the number of spatial streams applied to a corresponding RU. In addition, a third bit (e.g., B14) in the user field of the second format may include information related to whether a beamforming steering matrix is applied. A fourth bit (e.g., B15-B18) in the user field of the second format may include modulation and coding scheme (MCS) information. In addition, a fifth bit (e.g., B19) in the user field of the second format may include information related to whether dual carrier modulation (DCM) is applied. In addition, a sixth bit (i.e., B20) in the user field of the second format may include information related to a coding type (e.g., BCC or LDPC).

Hereinafter, a PPDU transmitted/received in a STA of the present specification will be described.

FIG. 10 illustrates an example of a PPDU used in the present specification.

The PPDU of FIG. 10 may be called in various terms such as an EHT PPDU, a TX PPDU, an RX PPDU, a first type or N-th type PPDU, or the like. For example, in the present specification, the PPDU or the EHT PPDU may be called in various terms such as a TX PPDU, a RX PPDU, a first type or N-th type PPDU, or the like. In addition, the EHT PPDU may be used in an EHT system and/or a new WLAN system enhanced from the EHT system.

The PPDU of FIG. 10 may indicate the entirety or part of a PPDU type used in the EHT system. For example, the example of FIG. 10 may be used for both of a single-user (SU) mode and a multi-user (MU) mode. In other words, the PPDU of FIG. 10 may be a PPDU for one receiving STA or a plurality of receiving STAs. When the PPDU of FIG. 10 is used for a trigger-based (TB) mode, the EHT-SIG of FIG. 10 may be omitted. In other words, an STA which has received a trigger frame for uplink-MU (UL-MU) may transmit the PPDU in which the EHT-SIG is omitted in the example of FIG. 10 .

In FIG. 10 , an L-STF to an EHT-LTF may be called a preamble or a physical preamble, and may be generated/transmitted/received/obtained/decoded in a physical layer.

A subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields of FIG. 10 may be determined as 312.5 kHz, and a subcarrier spacing of the EHT-STF, EHT-LTF, and Data fields may be determined as 78.125 kHz. That is, a tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be expressed in unit of 312.5 kHz, and a tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and Data fields may be expressed in unit of 78.125 kHz.

In the PPDU of FIG. 10 , the L-LTE and the L-STF may be the same as those in the conventional fields.

The L-SIG field of FIG. 10 may include, for example, bit information of 24 bits. For example, the 24-bit information may include a rate field of 4 bits, a reserved bit of 1 bit, a length field of 12 bits, a parity bit of 1 bit, and a tail bit of 6 bits. For example, the length field of 12 bits may include information related to a length or time duration of a PPDU. For example, the length field of 12 bits may be determined based on a type of the PPDU. For example, when the PPDU is a non-HT, HT, VHT PPDU or an EHT PPDU, a value of the length field may be determined as a multiple of 3. For example, when the PPDU is an HE PPDU, the value of the length field may be determined as “a multiple of 3”+1 or “a multiple of 3”+2. In other words, for the non-HT, HT, VHT PPDI or the EHT PPDU, the value of the length field may be determined as a multiple of 3, and for the HE PPDU, the value of the length field may be determined as “a multiple of 3”+1 or “a multiple of 3”+2.

For example, the transmitting STA may apply BCC encoding based on a 1/2 coding rate to the 24-bit information of the L-SIG field. Thereafter, the transmitting STA may obtain a BCC coding bit of 48 bits. BPSK modulation may be applied to the 48-bit coding bit, thereby generating 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to positions except for a pilot subcarrier{subcarrier index −21, −7, +7, +21} and a DC subcarrier{subcarrier index 0}. As a result, the 48 BPSK symbols may be mapped to subcarrier indices −26 to −22, −20 to −8, −6 to −1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map a signal of {−1, −1, −1, 1} to a subcarrier index{−28, −27, +27, +28}. The aforementioned signal may be used for channel estimation on a frequency domain corresponding to {−28, −27, +27, +28}.

The transmitting STA may generate an RL-SIG generated in the same manner as the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving STA may know that the RX PPDU is the HE PPDU or the EHT PPDU, based on the presence of the RL-SIG.

A universal SIG (U-SIG) may be inserted after the RL-SIG of FIG. 10 . The U-SIB may be called in various terms such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, a first (type) control signal, or the like.

The U-SIG may include information of N bits, and may include information for identifying a type of the EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two contiguous OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4 μs. Each symbol of the U-SIG may be used to transmit the 26-bit information. For example, each symbol of the U-SIG may be transmitted/received based on 52 data tomes and 4 pilot tones.

Through the U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 un-coded bits) may be transmitted. A first symbol of the U-SIG may transmit first X-bit information (e.g., 26 un-coded bits) of the A-bit information, and a second symbol of the U-SIB may transmit the remaining Y-bit information (e.g. 26 un-coded bits) of the A-bit information. For example, the transmitting STA may obtain 26 un-coded bits included in each U-SIG symbol. The transmitting STA may perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1/2 to generate 52-coded bits, and may perform interleaving on the 52-coded bits. The transmitting STA may perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols to be allocated to each U-SIG symbol. One U-SIG symbol may be transmitted based on 65 tones (subcarriers) from a subcarrier index −28 to a subcarrier index +28, except for a DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) except for pilot tones, i.e., tones −21, −7, +7, +21.

For example, the A-bit information (e.g., 52 un-coded bits) generated by the U-SIG may include a CRC field (e.g., a field having a length of 4 bits) and a tail field (e.g., a field having a length of 6 bits). The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits except for the CRC/tail fields in the second symbol, and may be generated based on the conventional CRC calculation algorithm. In addition, the tail field may be used to terminate trellis of a convolutional decoder, and may be set to, for example, “000000”.

The A-bit information (e.g., 52 un-coded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, the version-independent bits may have a fixed or variable size. For example, the version-independent bits may be allocated only to the first symbol of the U-SIG, or the version-independent bits may be allocated to both of the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be called in various terms such as a first control bit, a second control bit, or the like.

For example, the version-independent bits of the U-SIG may include a PHY version identifier of 3 bits. For example, the PHY version identifier of 3 bits may include information related to a PHY version of a TX/RX PPDU. For example, a first value of the PHY version identifier of 3 bits may indicate that the TX/RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits the EHT PPDU, the PHY version identifier of 3 bits may be set to a first value. In other words, the receiving STA may determine that the RX PPDU is the EHT PPDU, based on the PHY version identifier having the first value.

For example, the version-independent bits of the U-SIG may include a UL/DL flag field of 1 bit. A first value of the UL/DL flag field of 1 bit relates to UL communication, and a second value of the UL/DL flag field relates to DL communication.

For example, the version-independent bits of the U-SIG may include information related to a TXOP length and information related to a BSS color ID.

For example, when the EHT PPDU is divided into various types (e.g., various types such as an EHT PPDU related to an SU mode, an EHT PPDU related to a MU mode, an EHT PPDU related to a TB mode, an EHT PPDU related to extended range transmission, or the like), information related to the type of the EHT PPDU may be included in the version-dependent bits of the U-SIG.

For example, the U-SIG may include: 1) a bandwidth field including information related to a bandwidth; 2) a field including information related to an MCS scheme applied to EHT-SIG; 3) an indication field including information regarding whether a dual subcarrier modulation (DCM) scheme is applied to EHT-SIG; 4) a field including information related to the number of symbol used for EHT-SIG; 5) a field including information regarding whether the EHT-SIG is generated across a full band; 6) a field including information related to a type of EHT-LTF/STF; and 7) information related to a field indicating an EHT-LTF length and a CP length.

Preamble puncturing may be applied to the PPDU of FIG. 10 . The preamble puncturing implies that puncturing is applied to part (e.g., a secondary 20 MHz band) of the full band. For example, when an 80 MHz PPDU is transmitted, an STA may apply puncturing to the secondary 20 MHz band out of the 80 MHz band, and may transmit a PPDU only through a primary 20 MHz band and a secondary 40 MHz band.

For example, a pattern of the preamble puncturing may be configured in advance. For example, when a first puncturing pattern is applied, puncturing may be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when a second puncturing pattern is applied, puncturing may be applied to only any one of two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when a third puncturing pattern is applied, puncturing may be applied to only the secondary 20 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when a fourth puncturing is applied, puncturing may be applied to at least one 20 MHz channel not belonging to a primary 40 MHz band in the presence of the primary 40 MHz band included in the 80 MHaz band within the 160 MHz band (or 80+80 MHz band).

Information related to the preamble puncturing applied to the PPDU may be included in U-SIG and/or EHT-SIG. For example, a first field of the U-SIG may include information related to a contiguous bandwidth, and second field of the U-SIG may include information related to the preamble puncturing applied to the PPDU.

For example, the U-SIG and the EHT-SIG may include the information related to the preamble puncturing, based on the following method. When a bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured individually in unit of 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, a first field of the first U-SIG may include information related to a 160 MHz bandwidth, and a second field of the first U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the first 80 MHz band. In addition, a first field of the second U-SIG may include information related to a 160 MHz bandwidth, and a second field of the second U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the second 80 MHz band. Meanwhile, an EHT-SIG contiguous to the first U-SIG may include information related to a preamble puncturing applied to the second 80 MHz band (i.e., information related to a preamble puncturing pattern), and an EHT-SIG contiguous to the second U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the first 80 MHz band.

Additionally or alternatively, the U-SIG and the EHT-SIG may include the information related to the preamble puncturing, based on the following method. The U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) for all bands. That is, the EHT-SIG may not include the information related to the preamble puncturing, and only the U-SIG may include the information related to the preamble puncturing (i.e., the information related to the preamble puncturing pattern).

The U-SIG may be configured in unit of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG may be duplicated. That is, four identical U-SIGs may be included in the 80 MHz PPDU. PPDUs exceeding an 80 MHz bandwidth may include different U-SIGs.

The U-SIG may be configured in unit of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG may be duplicated. That is, four identical U-SIGs may be included in the 80 MHz PPDU. PPDUs exceeding an 80 MHz bandwidth may include different U-SIGs.

The EHT-SIG of FIG. 10 may include control information for the receiving STA. The EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 μs. Information related to the number of symbols used for the EHT-SIG may be included in the U-SIG.

The EHT-SIG may include a technical feature of the HE-SIG-B described with reference to FIG. 8 and FIG. 9 . For example, the EHT-SIG may include a common field and a user-specific field as in the example of FIG. 8 . The common field of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

As in the example of FIG. 8 , the common field of the EHT-SIG and the user-specific field of the EHT-SIG may be individually coded. One user block field included in the user-specific field may include information for two users, but a last user block field included in the user-specific field may include information for one user. That is, one user block field of the EHT-SIG may include up to two user fields. As in the example of FIG. 9 , each user field may be related to MU-MIMO allocation, or may be related to non-MU-MIMO allocation.

As in the example of FIG. 8 , the common field of the EHT-SIG may include a CRC bit and a tail bit. A length of the CRC bit may be determined as 4 bits. A length of the tail bit may be determined as 6 bits, and may be set to ‘000000’.

As in the example of FIG. 8 , the common field of the EHT-SIG may include RU allocation information. The RU allocation information may imply information related to a location of an RU to which a plurality of users (i.e., a plurality of receiving STAs) are allocated. The RU allocation information may be configured in unit of 8 bits (or N bits), as in Table 1.

The example of Table 5 to Table 7 is an example of 8-bit (or N-bit) information for various RU allocations. An index shown in each table may be modified, and some entries in Table 5 to Table 7 may be omitted, and entries (not shown) may be added.

The example of Table 5 to Table 7 relates to information related to a location of an RU allocated to a 20 MHz band. For example, ‘an index 0’ of Table 5 may be used in a situation where nine 26-RUs are individually allocated (e.g., in a situation where nine 26-RUs shown in FIG. 5 are individually allocated).

Meanwhile, a plurality or RUs may be allocated to one STA in the EHT system. For example, regarding ‘an index 60’ of Table 6, one 26-RU may be allocated for one user (i.e., receiving STA) to the leftmost side of the 20 MHz band, one 26-RU and one 52-RU may be allocated to the right side thereof, and five 26-RUs may be individually allocated to the right side thereof.

TABLE 5 Number Indices #1 #2 #3 #4 #5 #6 #7 #8 #9 of entries 0 26 26 26 26 26 26 26 26 26 1 1 26 26 26 26 26 26 26 52 1 2 26 26 26 26 26 52 26 26 1 3 26 26 26 26 26 52 52 1 4 26 26 52 26 26 26 26 26 1 5 26 26 52 26 26 26 52 1 6 26 26 52 26 52 26 26 1 7 26 26 52 26 52 52 1 8 52 26 26 26 26 26 26 26 1 9 52 26 26 26 26 26 52 1 10 52 26 26 26 52 26 26 1 11 52 26 26 26 52 52 1 12 52 52 26 26 26 26 26 1 13 52 52 26 26 26 52 1 14 52 52 26 52 26 26 1 15 52 52 26 52 52 1 16 26 26 26 26 26 106 1 17 26 26 52 26 106 1 18 52 26 26 26 106 1 19 52 52 26 106 1

TABLE 6 Number Indices #1 #2 #3 #4 #5 #6 #7 #8 #9 of entries 20 106 26 26 26 26 26 1 21 106 26 26 26 52 1 22 106 26 52 26 26 1 23 106 26 52 52 1 24 52 52 — 52 52 1 25 242-tone RU empty (with zero users) 1 26 106 26 106 1 27-34 242 8 35-42 484 8 43-50 996 8 51-58 2*996 8 59 26 26 26 26 26 52 + 26 26 1 60 26 26 + 52 26 26 26 26 26 1 61 26 26 + 52 26 26 26 52 1 62 26 26 + 52 26 52 26 26 1 63 26 26 52 26 52 + 26 26 1 64 26 26 + 52 26 52 + 26 26 1 65 26 26 + 52 26 52 52 1

TABLE 7 66 52 26 26 26 52 + 26 26 1 67 52 52 26 52 + 26 26 1 68 52 52 + 26 52 52 1 69 26 26 26 26 26 + 106 1 70 26 26 + 52 26 106 1 71 26 26 52 26 + 106 1 72 26 26 + 52 26 + 106 1 73 52 26 26 26 + 106 1 74 52 52 26 + 106 1 75 106 + 26 26 26 26 26 1 76 106 + 26 26 26 52 1 77 106 + 26 52 26 26 1 78 106 26 52 + 26 26 1 79 106 + 26 52 + 26 26 1 80 106 + 26 52 52 1 81 106 + 26 106 1 82 106 26 + 106 1

A mode in which the common field of the EHT-SIG is omitted may be supported. The mode in the common field of the EHT-SIG is omitted may be called a compressed mode. When the compressed mode is used, a plurality of users (i.e., a plurality of receiving STAs) may decode the PPDU (e.g., the data field of the PPDU), based on non-OFDMA. That is, the plurality of users of the EHT PPDU may decode the PPDU (e.g., the data field of the PPDU) received through the same frequency band. Meanwhile, when a non-compressed mode is used, the plurality of users of the EHT PPDU may decode the PPDU (e.g., the data field of the PPDU), based on OFDMA. That is, the plurality of users of the EHT PPDU may receive the PPDU (e.g., the data field of the PPDU) through different frequency bands.

The EHT-SIG may be configured based on various MCS schemes. As described above, information related to an MCS scheme applied to the EHT-SIG may be included in U-SIG. The EHT-SIG may be configured based on a DCM scheme. For example, among N data tones (e.g., 52 data tones) allocated for the EHT-SIG, a first modulation scheme may be applied to half of consecutive tones, and a second modulation scheme may be applied to the remaining half of the consecutive tones. That is, a transmitting STA may use the first modulation scheme to modulate specific control information through a first symbol and allocate it to half of the consecutive tones, and may use the second modulation scheme to modulate the same control information by using a second symbol and allocate it to the remaining half of the consecutive tones. As described above, information (e.g., a 1-bit field) regarding whether the DCM scheme is applied to the EHT-SIG may be included in the U-SIG. An HE-STF of FIG. 10 may be used for improving automatic gain control estimation in a multiple input multiple output (MIMO) environment or an OFDMA environment. An HE-LTF of FIG. 10 may be used for estimating a channel in the MIMO environment or the OFDMA environment.

The EHT-STF of FIG. 10 may be set in various types. For example, a first type of STF (e.g., 1× STF) may be generated based on a first type STF sequence in which a non-zero coefficient is arranged with an interval of 16 subcarriers. An STF signal generated based on the first type STF sequence may have a period of 0.8 μs, and a periodicity signal of 0.8 μs may be repeated 5 times to become a first type STF having a length of 4 μs. For example, a second type of STF (e.g., 2× STF) may be generated based on a second type STF sequence in which a non-zero coefficient is arranged with an interval of 8 subcarriers. An STF signal generated based on the second type STF sequence may have a period of 1.6 μs, and a periodicity signal of 1.6 μs may be repeated 5 times to become a second type STF having a length of 8 μs. Hereinafter, an example of a sequence for configuring an EHT-STF (i.e., an EHT-STF sequence) is proposed. The following sequence may be modified in various ways.

The EHT-STF may be configured based on the following sequence M.

M={−1,−1,−1,1,1,1,−1,1,1,1,−1,1,1,−1,1}  <Equation 1>

The EHT-STF for the 20 MHz PPDU may be configured based on the following equation. The following example may be a first type (i.e., 1× STF) sequence. For example, the first type sequence may be included in not a trigger-based (TB) PPDU but an EHT-PPDU. In the following equation, (a:b:c) may imply a duration defined as b tone intervals (i.e., a subcarrier interval) from a tone index (i.e., subcarrier index) ‘a’ to a tone index ‘c’. For example, the equation 2 below may represent a sequence defined as 16 tone intervals from a tone index −112 to a tone index 112. Since a subcarrier spacing of 78.125 kHz is applied to the EHT-STR, the 16 tone intervals may imply that an EHT-STF coefficient (or element) is arranged with an interval of 78.125*16=1250 kHz. In addition,*implies multiplication, and sqrt( ) implies a square root. In addition, j implies an imaginary number.

EHT-STF(−112:16:112)={M}*(1+j)/sqrt(2)

EHT-STF(0)=0  <Equation 2>

The EHT-STF for the 40 MHz PPDU may be configured based on the following equation. The following example may be the first type (i.e., 1× STF) sequence.

EHT-STF(−240:16:240)={M,0,−M}*(1+j)/sqrt(2)  <Equation 3>

The EHT-STF for the 80 MHz PPDU may be configured based on the following equation. The following example may be the first type (i.e., 1× STF) sequence.

EHT-STF(−496:16:496)={M,1,−M,0,−M,1,−M}*(1+j)/sqrt(2)  <Equation 4>

The EHT-STF for the 160 MHz PPDU may be configured based on the following equation. The following example may be the first type (i.e., 1× STF) sequence.

EHT-STF(−1008:16:1008)={M,1,−M,0,−M,1,−M,0,−M,−1,M,0,−M,1,−M}*(1+j)/sqrt(2)  <Equation 5>

In the EHT-STF for the 80+80 MHz PPDU, a sequence for lower 80 MHz may be identical to Equation 4. In the EHT-STF for the 80+80 MHz PPDU, a sequence for upper 80 MHz may be configured based on the following equation.

EHT-STF(−496:16:496)={−M,−1,M,0,—M,1,—M}*(1+j)/sqrt(2)  <Equation 6>

Equation 7 to Equation 11 below relate to an example of a second type (i.e., 2× STF) sequence.

EHT-STF(−120:8:120)={M,0,−M}*(1+j)/sqrt(2)  <Equation 7>

The EHT-STF for the 40 MHz PPDU may be configured based on the following equation.

EHT-STF(−248:8:248)={M,−1,−M,0,M,−1,M}*(1+j)/sqrt(2)

EHT-STF(−248)=0

EHT-STF(248)=0  <Equation 8>

The EHT-STF for the 80 MHz PPDU may be configured based on the following equation.

EHT-STF(−504:8:504)={M,−1,M,−1,−M,−1,M,0,−M,1,M,1,−M,1,−M}*(1+j)/sqrt(2)  <Equation 9>

The EHT-STF for the 160 MHz PPDU may be configured based on the following equation.

EHT-STF(−1016:16:1016)={M,−1,M,−1,−M,−1,M,0,−M,1,M,1,−M,1,−M,0,−M,1,−M,1,M,1,−M,0,−M,1,M,1,−M,1,−M}*(1+j)/sqrt(2)

EHT-STF(−8)=0, EHT-STF(8)=0,

EHT-STF(−1016)=0, EHT-STF(1016)=0<Equation 10>

In the EHT-STF for the 80+80 MHz PPDU, a sequence for lower 80 MHz may be identical to Equation 9. In the EHT-STF for the 80+80 MHz PPDU, a sequence for upper 80 MHz may be configured based on the following equation.

EHT-STF(−504:8:504)={−M,1,−M,1,M,1,−M,0,−M,1,M,1,−M,1,−M}*(1+j)/sqrt(2)

EHT-STF(−504)=0,

EHT-STF(504)=0<  Equation 11>

The EHT-LTF may have first, second, and third types (i.e., 1×, 2×, 4× LTF). For example, the first/second/third type LTF may be generated based on an LTF sequence in which a non-zero coefficient is arranged with an interval of 4/2/1 subcarriers. The first/second/third type LTF may have a time length of 3.2/6.4/12.8 μs. In addition, a GI (e.g., 0.8/1/6/3.2 μs) having various lengths may be applied to the first/second/third type LTF.

Information related to a type of STF and/or LTF (information related to a GI applied to LTF is also included) may be included in a SIG-A field and/or SIG-B field or the like of FIG. 10 .

A PPDU (e.g., EHT-PPDU) of FIG. 10 may be configured based on the example of FIG. 5 and FIG. 6 .

For example, an EHT PPDU transmitted on a 20 MHz band, i.e., a 20 MHz EHT PPDU, may be configured based on the RU of FIG. 5 . That is, a location of an RU of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown in FIG. 5 .

An EHT PPDU transmitted on a 40 MHz band, i.e., a 40 MHz EHT PPDU, may be configured based on the RU of FIG. 6 . That is, a location of an RU of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown in FIG. 6 .

Since the RU location of FIG. 6 corresponds to 40 MHz, a tone-plan for 80 MHz may be determined when the pattern of FIG. 6 is repeated twice. That is, an 80 MHz EHT PPDU may be transmitted based on a new tone-plan in which not the RU of FIG. 7 but the RU of FIG. 6 is repeated twice.

When the pattern of FIG. 6 is repeated twice, 23 tones (i.e., 11 guard tones+12 guard tones) may be configured in a DC region. That is, a tone-plan for an 80 MHz EHT PPDU allocated based on OFDMA may have 23 DC tones. Unlike this, an 80 MHz EHT PPDU allocated based on non-OFDMA (i.e., a non-OFDMA full bandwidth 80 MHz PPDU) may be configured based on a 996-RU, and may include 5 DC tones, 12 left guard tones, and 11 right guard tones.

A tone-plan for 160/240/320 MHz may be configured in such a manner that the pattern of FIG. 6 is repeated several times.

The PPDU of FIG. 10 may be determined (or identified) as an EHT PPDU based on the following method.

A receiving STA may determine a type of an RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the EHT PPDU: 1) when a first symbol after an L-LTF signal of the RX PPDU is a BPSK symbol; 2) when RL-SIG in which the L-SIG of the RX PPDU is repeated is detected; and 3) when a result of applying “modulo 3” to a value of a length field of the L-SIG of the RX PPDU is detected as “0”. When the RX PPDU is determined as the EHT PPDU, the receiving STA may detect a type of the EHT PPDU (e.g., an SU/MU/Trigger-based/Extended Range type), based on bit information included in a symbol after the RL-SIG of FIG. 10 . In other words, the receiving STA may determine the RX PPDU as the EHT PPDU, based on: 1) a first symbol after an L-LTF signal, which is a BPSK symbol; 2) RL-SIG contiguous to the L-SIG field and identical to L-SIG; 3) L-SIG including a length field in which a result of applying “modulo 3” is set to “0”; and 4) a 3-bit PHY version identifier of the aforementioned U-SIG (e.g., a PHY version identifier having a first value).

For example, the receiving STA may determine the type of the RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the HE PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; 2) when RL-SIG in which the L-SIG is repeated is detected; and 3) when a result of applying “modulo 3” to a value of a length field of the L-SIG is detected as “1” or “2”.

For example, the receiving STA may determine the type of the RX PPDU as a non-HT, HT, and VHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; and 2) when RL-SIG in which L-SIG is repeated is not detected. In addition, even if the receiving STA detects that the RL-SIG is repeated, when a result of applying “modulo 3” to the length value of the L-SIG is detected as “0”, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU.

In the following example, a signal represented as a (TX/RX/UL/DL) signal, a (TX/RX/UL/DL) frame, a (TX/RX/UL/DL) packet, a (TX/RX/UL/DL) data unit, (TX/RX/UL/DL) data, or the like may be a signal transmitted/received based on the PPDU of FIG. 10 . The PPDU of FIG. 10 may be used to transmit/receive frames of various types. For example, the PPDU of FIG. 10 may be used for a control frame. An example of the control frame may include a request to send (RTS), a clear to send (CTS), a power save-poll (PS-poll), BlockACKReq, BlockAck, a null data packet (NDP) announcement, and a trigger frame. For example, the PPDU of FIG. 10 may be used for a management frame. An example of the management frame may include a beacon frame, a (re-)association request frame, a (re-)association response frame, a probe request frame, and a probe response frame. For example, the PPDU of FIG. 10 may be used for a data frame. For example, the PPDU of FIG. 10 may be used to simultaneously transmit at least two or more of the control frames, the management frame, and the data frame.

FIG. 11 illustrates an example of a modified transmission device and/or receiving device of the present specification.

Each device/STA of the sub-figure (a)/(b) of FIG. 1 may be modified as shown in FIG. 11 . A transceiver 630 of FIG. 11 may be identical to the transceivers 113 and 123 of FIG. 1 . The transceiver 630 of FIG. 11 may include a receiver and a transmitter.

A processor 610 of FIG. 11 may be identical to the processors 111 and 121 of FIG. 1 . Alternatively, the processor 610 of FIG. 11 may be identical to the processing chips 114 and 124 of FIG. 1 .

A memory 620 of FIG. 11 may be identical to the memories 112 and 122 of FIG. 1 . Alternatively, the memory 620 of FIG. 11 may be a separate external memory different from the memories 112 and 122 of FIG. 1 .

Referring to FIG. 11 , a power management module 611 manages power for the processor 610 and/or the transceiver 630. A battery 612 supplies power to the power management module 611. A display 613 outputs a result processed by the processor 610. A keypad 614 receives inputs to be used by the processor 610. The keypad 614 may be displayed on the display 613. A SIM card 615 may be an integrated circuit which is used to securely store an international mobile subscriber identity (IMSI) and its related key, which are used to identify and authenticate subscribers on mobile telephony devices such as mobile phones and computers.

Referring to FIG. 11 , a speaker 640 may output a result related to a sound processed by the processor 610. A microphone 641 may receive an input related to a sound to be used by the processor 610.

1. Subchannel Selective Transmission (SST) Mechanism and LTF Sequence

The HE STA supporting the HE SST operation shall set dot11HESbchannelSelectiveTransmissionImplemented to true and set the HE Subchannel selective transmission support field of the HE Capabilities element transmitted by itself to 1.

The HE STA that does not support the HE SST operation shall set the HE Subchannel Selective Transmission Support field to 0 in the HE Capabilities element transmitted by itself.

Target wake time (TWT) allows the AP to manage activity in the BSS to minimize contention between STAs and reduce the time required for STAs using power saving mode to stay awake. This is achieved by allocating STAs to operate at non-overlapping times and/or frequencies and focusing frame exchanges on predefined service periods. The HE STA negotiates individual TWT agreements with other HE STAs.

The HE SST non-AP STA and the HE SST AP may set the SST operation by negotiating the trigger activation TWT defined in the individual TWT contract, except for the following.

-   -   The TWT request may have a TWT channel field with a maximum of 1         bit set to 1 to indicate a secondary channel requested to         include an RU assignment addressed to a HE SST non-AP STA that         is a 20 MHz operating STA.     -   The TWT request may have a TWT channel field with all four LSBs         or all four MSBs set to 1 to indicate whether the primary 80 MHz         channel or the secondary 80 MHz channel is requested to include         the RU allocation addressed to the HE SST non-AP STA that is the         80 MHz operating STA.     -   The TWT response shall have a TWT channel field with a maximum         of 1 bit set to 1 to indicate the secondary channel that will         contain the RU assignment addressed to the HE SST non-AP STA         that is the 20 MHz operating STA.     -   The TWT response shall have a TWT channel field including all         four LSBs or all four MSBs indicating whether the primary 80 MHz         channel or the secondary 80 MHz channel includes the RU         allocation addressed to the HE SST non-AP STA that is the 80 MHz         operating STA.

The HE SST AP and the HE SST non-AP STA implicitly terminate the trigger activation TWT if HE SST AP changes the working channel or channel width and the secondary channel of the trigger-activated TWT is not within the new working channel or channel width.

The HE SST non-AP STA follows the rules of the individual TWT contract to exchange frames with the HE SST AP during trigger activation TWT SP. However, the following conditions are excluded.

-   -   The STA shall be available on the subchannel indicated in the         TWT channel field of the TWT response at the TWT start time.     -   The STA shall not access the medium of the subchannel using DCF         or EDCAF.     -   The STA shall not respond to a trigger frame addressed to it         unless it performs CCA until a frame capable of setting NAV is         detected, or until a period equal to NAVSyncDelay occurs         (whichever is earlier).     -   When the STA receives a PPDU in a subchannel, it must update the         NAV according to two NAV updates.

That is, according to the SST mechanism, the HE SST AP and the HE SST non-AP STA may access a specific subchannel (or secondary channel) during the trigger-enabled TWT SP.

The LTF sequence defined in the 802.11ax wireless LAN system is as follows.

First, in 80 MHz transmission, a 1× HE-LTF sequence is defined as follows.

HE-LTF(−500:500)={−1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, 0, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1}

In 80 MHz transmission, a 2× HE-LTF sequence is defined as follows.

HE-LTF(−500:500)={+1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, 0, 0, 0, 0, 0, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1}

In 80 MHz transmission, the 4× HE-LTF sequence is defined as follows.

HE-LTF(−500:500)={+1, +1, −1, +1, −1, +1, −1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, −1, −1, +1, +1, +1, +1, +1, +1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, +1, +1, +1, +1, +1, +1, +1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, +1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, +1, −1, −1, −1, −1, −1, −1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, +1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1+1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, −1, +1, −1, −1, −1, −1, +1, +1, +1, −1, −1, +1, 0, 0, 0, 0, 0, +1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, +1, +1, +1, +1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, +1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, −1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, −1, −1, −1, −1, −1, −1, −1, 1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, +1}

In 160 MHz transmission, the 1× HE-LTF sequence is defined as follows.

HE-LTF(−1012:1012)={LTF80MHz_lower_1×, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, LTF80MHz_upper_1×}

Here, the configuration sequence is defined as follows.

LTF80MHz_lower_1×={LTF80MHz_left_1×, 0, LTF80MHz_right_1×}

LTF80MHz_upper_1×={LTF80MHz_left_1×, 0, −LTF80MHz_right_1×}

LTF80MHz_left_1×={−1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0}

LTF80MHz_right_1×={0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, −1, 0, 0, 0, +1, 0, 0, 0, +1}

In 160 MHz transmission, a 2× HE-LTF sequence is defined as follows.

HE-LTF(−1012:1012)={LTF80MHz_lower_2×, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, LTF80MHz_upper_2×}

Here, the configuration sequence is defined as follows.

LTF80MHz_lower_2×={LTF80MHz_part1_2×, LTF80MHz_part2_2×, LTF80MHz_part3_2×, LTF80MHz_part4_2×, LTF80MHz_part5_2×}

LTF80MHz_upper_2×={LTF80MHz_part1_2×, −LTF80MHz_part2_2×, LTF80MHz_part3_2×, LTF80MHz_part4_2×, −LTF80MHz_part5_2×}

LTF80MHz_part1_2×={+1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0}

LTF80MHz_part2_2×={+1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0}

LTF80MHz_part2_3×={+1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, 0, 0, 0, 0, 0, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1}

LTF80MHz_part2_4×={0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1}

LTF80MHz_part2_5×={0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, −1, 0, −1, 0, +1, 0, −1, 0, −1, 0, −1, 0, +1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1, 0, +1, 0, −1, 0, +1, 0, +1}

In 160 MHz transmission, a 4× HE-LTF sequence is defined as follows.

HE-LTF(−1012:1012)={LTF80MHz_lower_4×, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, LTF80MHz_upper_4×}

Here, the configuration sequence is defined as follows.

LTF80MHz_lower_4×={LTF80MHz_left_4×, 0, LTF80MHz_right_4×}

LTF80MHz_upper_4×={LTF80MHz_left_4×, 0, −LTF80MHz_right_4×}

LTF80MHz_left_4×={+1, +1, −1, +1, −1, +1, −1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, −1, −1, +1, +1, +1, +1, +1, +1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, +1, +1, +1, +1, +1, +1, +1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, +1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, +1, −1, −1, −1, −1, −1, −1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, +1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, −1, +1, −1, −1, −1, −1, +1, +1, +1, −1, −1, +1, 0, 0}

LTF80MHz_right_4×={0, 0, +1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, +1, +1, +1, +1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, +1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, +1, +1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, −1, +1, −1, +1, −1, +1, +1, +1, +1, +1, −1, −1, −1, +1, +1, +1, +1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, −1, +1, +1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, −1, −1, +1, −1, −1, +1, −1, +1, −1, +1, −1, +1, −1, −1, +1, +1, −1, +1, −1, +1, +1, +1, −1, −1, +1, −1, −1, −1, +1, −1, −1, −1, −1, −1, −1, −1, +1, −1, +1, +1, −1, +1, +1, −1, +1, −1, −1, −1, +1, +1, −1, +1, +1, +1, −1, −1, +1, +1, +1, +1, +1, −1, +1, −1, −1, −1, −1, +1, +1, −1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, +1, −1, +1, −1, +1, −1, −1, −1, −1, −1, +1, +1, +1, −1, −1, −1, −1, +1, −1, −1, +1, +1, +1, −1, +1, +1, −1, −1, +1, −1, +1, −1, +1}

2. Examples Applicable to the Present Specification

In the WLAN 802.11 system, in order to increase peak throughput, it is considered to use a wider band than the existing 802.11ax or to transmit an increased stream by using more antennas. In addition, a method of using various bands by aggregation is also being considered.

This specification proposes a method of indicating BW in an aggregated PPDU in which an HE PPDU and an EHT PPDU are simultaneously transmitted in a situation in which a broadband is considered.

FIG. 12 is a diagram of a representative Aggregated PPDU.

Referring to FIG. 12 , each Sub-PPDU may be a HE PPDU/EHT PPDU/post-EHT (EHT+) PPDU. However, it may be preferable that the HE PPDU is transmitted within the primary 160 MHz. In addition, it may be desirable to transmit the same type of Sub-PPDU within the primary 160 MHz and the secondary 160 MHz. By the SST mechanism, each STA can be allocated to a specific band of 80 MHz or higher, a sub-PPDU for each STA may be transmitted, or each STA may transmit a sub-PPDU in the corresponding band. FIG. 10 shows a representative EHT MU PPDU format.

FIG. 13 shows an example of the structure of U-SIG.

The U-SIG is divided into a version independent field and a version dependent field as shown in FIG. 13 .

Bandwidth field can be used to indicate bandwidth, which can be included in the version independent field of Universal-SIG (U-SIG). Additionally, in addition to the bandwidth field, a 20 MHz-based preamble puncturing pattern within the corresponding 80 MHz at each 80 MHz may also be indicated. This may help STAs decoding a specific 80 MHz to decode the EHT-SIG. Therefore, assuming that such information is loaded on the U-SIG, the configuration of the U-SIG may change every 80 MHz.

In addition, the version independent field may include a 3-bit version identifier indicating a Wi-Fi version after 802.11be and 802.11be, a 1-bit DL/UL field, a BSS color, a TXOP duration, and the like, the version dependent field may include information such as a PPDU type. In U-SIG, two symbols are jointly encoded, and U-SIG consists of 52 data tones and 4 pilot tones for each 20 MHz. Also, U-SIG is modulated in the same way as HE-SIG-A. That is, the U-SIG is modulated with a BPSK 1/2 code rate. In addition, the EHT-SIG may be divided into a common field and a user specific field, and may be encoded as a variable MCS. The EHT-SIG may have a 1 2 1 2 . . . structure in units of 20 MHz as in the existing 802.11ax (or it may be configured in another structure. For example, 1 2 3 4 . . . or 1 2 1 2 3 4 3 4 . . . .). In addition, the EHT-SIG may be configured in units of 80 MHz, and in a bandwidth of 80 MHz or more, the EHT-SIG may be duplicated in units of 80 MHz or may be configured with different information in units of 80 MHz.

In the present specification, when an aggregated PPDU is configured of HE and EHT PPDUs, a BW indication method in each sub-PPDU is proposed. The advantage of A-PPDU is that when simultaneously supporting HE/EHT (/EHT+) STAs, it is possible to simultaneously support the PPDU by maximizing the version of each STA rather than the HE PPDU (EHT or EHT+ STA may also use the HE Sub-PPDU within the A-PPDU, and the PPDU may be located in a channel different from the HE Sub-PPDU for the HE STA, it may be supported together with the HE STA using the MU HE Sub-PPDU in the same channel). By performing transmission using the A-PPDU in this way, transmission efficiency can be further increased. In this case, the BW may be indicated differently for each sub-PPDU, and accordingly, the BW may vary according to the configuration of the sub-PPDU. First, the configuration of the Sub-PPDU is proposed.

In the present specification, it is assumed that each Sub PPDU is a DL (downlink) PPDU, but is not limited thereto and may be a TB (trigger-based) PPDU that is UL (uplink) transmission.

2.1. Sub-PPDU Configuration

The following configuration can be suggested.

2.1.1. Different Sub-PPDU Configuration for Every 80 MHz

Since the SST Allocates STAs Based on 80 MHz Units, Different Sub-PPDUs May be configured for each 80 MHz. However, the HE Sub-PPDU for the HE STA may be located in P80 (primary 80 MHz channel) or S80 (secondary 80 MHz channel).

This approach may be desirable from an implementation point of view.

2.1.2. Multiple Consecutive 80 MHz Sub-PPDUs of the Same Version are Also Configured as One Sub-PPDU

Sub-PPDUs of the same version (HE or EHT or EHT+) of several consecutive 80 MHz may be configured as one Sub-PPDU. For example, Sub-PPDU-1 in FIG. 12 may be one example. However, the Sub-PPDU for the HE STA may be located at P80 or P160.

This method may be preferable in terms of supporting STAs allocated to a wide band.

2.1.3. Multiple Non-Consecutive 80 MHz Sub-PPDUs of the Same Version are Also Configured as One Sub-PPDU

Several non-consecutive 80 MHz sub-PPDUs of the same version may also be configured as one sub-PPDU. For example, in FIG. 12 , if Sub-PPDU-1 and Sub-PPDU-3 are the same version, it may be regarded as one Sub-PPDU. However, the Sub-PPDU for the HE STA may be located at P80 or P160.

This method may be preferable in terms of supporting STAs allocated to a wide band or in terms of flexible channel allocation to STAs.

2.1.4. Configuration by Limiting Only HE Sub-PPDUs within the Primary 160 MHz

When an 802.11ax STA having a specific 160 MHz capability detects a signal in the entire 160 MHz channel, the STA may perform decoding by combining L-SIG and HE-SIG-A. In this case, if the HE sub-PPDU and the EHT (or EHT+) sub-PPDU are mixed within the primary 160 MHz, a decoding problem may occur in the STA. Therefore, when configuring the A-PPDU, only the HE Sub-PPDU may be configured within the primary 160 MHz and only the EHT Sub-PPDU may be configured within the secondary 160 MHz. EHT+Sub-PPDU exists only in channels other than Primary 160 MHz. Other channels may be determined by max BW (Bandwidth).

2.1.5. Each 160 MHz Channel Always Consists of the Same Sub-PPDU

As in 2.1.4, when an 802.11ax STA with a specific 160 MHz capability detects a signal in the entire 160 MHz channel, the STA may perform by combining L-SIG and HE-SIG-A. In this case, if different sub-PPDUs are mixed within a specific 160 MHz, a decoding problem may occur in the STA. Therefore, when configuring A-PPDU, each 160 MHz channel can always consist of the same sub-PPDU. In particular, only HE Sub-PPDUs can be configured within the primary 160 MHz, and only the EHT (or EHT+) sub-PPDUs can be configured within the secondary 160 MHz. (However, if the contents of L-SIG and U-SIG of EHT+Sub-PPDU and EHT Sub-PPDU are the same, EHT and EHT+Sub-PPDU may be mixed in the 160 MHz channel). Conversely, only EHT (or EHT+) Sub-PPDUs can be configured within Primary 160 MHz and only HE Sub-PPDUs can be configured within Secondary 160 MHz, but considering that the maximum BW supported by HE is 160 MHz (in HE, secondary 160 MHz is not present) may be an undesirable configuration.

In addition, the following situations can also be considered: Only HE Sub-PPDUs may be configured within the primary 160 MHz, and only the HE Sub-PPDUs may be configured within the secondary 160 MHz. The difference between HE Sub-PPDUs within each 160 MHz is that the HE Sub-PPDU within the primary 160 MHz is an HE Sub-PPDU for the HE STA and EHT (or EHT+) STA, whereas the HE Sub-PPDU within the secondary 160 MHz is an HE Sub-PPDU for only the EHT (or EHT+) STA. If most of the adjacent OBSS or non-associated STAs are HE STAs, there may be an advantage in that the TXOP field of the HE Sub-PPDU can be decoded and utilized, but this may be an undesirable configuration for an EHT (or EHT+) STA that receives or transmits the HE Sub-PPDU.

Below, the BW indicator is proposed.

2.2. BW Indication Method

It can be indicated as follows.

2.2.1. Indicated by Sub-PPDU BW

Regardless of how each Sub-PPDU is configured in 2.1, it may be indicated by its own BW. For example, in FIG. 12 , the BW indicator may indicate the bandwidth of Sub-PPDU-1 as 160 MHz, the bandwidth of Sub-PPDU-2 as 80 MHz, and the bandwidth of Sub-PPDU-3 as 80 MHz.

This may be easy in terms of implementation.

2.2.2. Indicated by BW of Sub-PPDUs of the Same Version

Regardless of how each Sub-PPDU is configured in 2.1, each Sub-PPDU may be indicated by the total BW of the Sub-PPDUs of the same version. For example, in FIG. 12 , if Sub-PPDU-1 is an HE PPDU and Sub-PPDU-2 and Sub-PPDU-3 are EHT-PPDUs, the BW indicator indicates the bandwidth of Sub-PPDU-1 as 160 MHz and the bandwidth of Sub-PPDU-2 and Sub-PPDU-3 as 160 MHz respectively. As another example, in FIG. 12 , if Sub-PPDU-2 is an HE PPDU and Sub-PPDU-1 and Sub-PPDU-3 are EHT-PPDUs, the BW indicator indicates the bandwidth of Sub-PPDU-2 as 80 MHz and the bandwidths of PPDU-1 and Sub-PPDU-3 as 240 MHz (Alternatively, 320 MHz may be indicated, and 80 MHz puncturing may be additionally indicated), respectively.

This may be complicated in implementation, but there may be an advantage in that HE-STF/HE-LTF/EHT-STF/EHT-LTF can be configured in a way that can appropriately lower PAPR.

2.2.3. Sub-PPDU for EHT STA (or EHT+STA) is Indicated by the Total BW of the Aggregated PPDU.

Regardless of how each Sub-PPDU is configured in 2.1, the bandwidth of the Sub-PPDU for the EHT-STA may be indicated by the total BW of the Aggregated PPDU. For example, in FIG. 12 , if Sub-PPDU-1 is an HE PPDU and Sub-PPDU-2 and Sub-PPDU-3 are EHT-PPDUs, the BW indicator indicates the bandwidth of Sub-PPDU-1 as 160 MHz and the Bandwidths of Sub-PPDU-2 and Sub-PPDU-3 as 320 MHz, respectively. As another example, in FIG. 12 , if Sub-PPDU-2 is an HE PPDU and Sub-PPDU-1 and Sub-PPDU-3 are EHT-PPDUs, the BW indicator indicates the bandwidth of Sub-PPDU-2 as 80 MHz and the bandwidths of Sub-PPDU-1 and Sub-PPDU-3 as 320 MHz, respectively.

This may be complicated in implementation, but it allows OBSS (Overlapping Basic Service Set) STAs or STAs in BSS not participating in transmission to acquire the bandwidth used for Aggregated PPDU transmission (total BW is 320 MHz). By preventing transmission within the A-PPDU bandwidth in the corresponding channel and the adjacent channel, interference can be effectively blocked. However, when the OBSS STA (or the STA in the BSS that is not participating in the transmission) has wide bandwidth (320 MHz) capability, combining and decoding the entire A-PPDU according to the BW indicator, a decoding error (e.g., an error in which the modulo value of the Length field of the L-SIG changes) may occur due to different contents of each Sub PPDU.

2.2.4. BW Fixed

The BW of the Sub-PPDU for the HE STA may always be fixed to 160 MHz regardless of the actual BW. This may be the case only when it is assumed that the total BW is 160 MHz or more. In addition, the BW of the Sub-PPDU for the EHT (EHT+) STA may always be fixed to 320 MHz (the maximum BW of EHT+ in the case of EHT+) regardless of the actual BW. This is the simplest method and can be efficient in the configuration of sequences, etc.

2.3. Configuration and BW Indication when Considering SST

BW indication in the case of considering SST may be additionally considered. Considering the SST, the HE STA may be allocated to any 80 MHz within the primary 160 MHz (i.e., the primary 80 MHz or the secondary 80 MHz), and the EHT STA may be allocated to any 80 MHz within the 320 MHz channel. In addition, the EHT+STA may be allocated to any 80 MHz within the maximum possible BW channel of the EHT+. For example, the HE STA may be allocated to the secondary 80 MHz and the EHT STA may be allocated to the primary 80 MHz. If the HE STA is allocated to the primary 80 MHz, the BW may be indicated by the method 2.2 above, so it is not considered here.

If the HE STA is allocated to the secondary 80 MHz, the BW of the sub-PPDU for the HE may always be indicated as 160 MHz. If the EHT (or EHT+) STA is allocated only to the primary 80 MHz, the bandwidth of the Sub-PPDU for this may be indicated as 80 MHz or full BW (160 MHz) or 320 MHz (the maximum BW of EHT+ in the case of EHT+) as in the method of 2.2. If the EHT (or EHT+) STA is allocated only to the secondary 160 MHz, the bandwidth of the Sub-PPDU for this is 160 MHz or the entire BW (indicates 240 MHz or 320 MHz and additional puncturing indicator can be considered) or 320 MHz (in case of EHT+, the maximum BW of EHT+). If the EHT (or EHT+) STA is allocated to the primary 80 MHz and the secondary 160 MHz, the bandwidth of the Sub-PPDU for this is the total BW (indicates 320 MHz, additional puncturing indicator can be considered) or 320 MHz (in case of EHT+, the maximum BW of EHT+).

2.4. In the Case of Limiting Only HE Sub-PPDUs within the Primary 160 MHz, and in Case of Always Configuring the Same Sub-PPDUs in Each 160 MHz Channel

Consider that only HE Sub-PPDUs are configured in Primary 160 MHz, which is one of the configuration methods of 2.1.4 or 2.1.5, and only EHT (or EHT+) Sub-PPDUs are configured in Secondary 160 MHz. In this case, BW may be set as in method 2.2 above. That is, HE may be set to 80 MHz or 160 MHz or BW in which all HE Sub-PPDUs are used, and EHT (EHT+) may be set to 80 MHz, or all EHT (EHT+) BW using Sub-PPDU, or full BW of A-PPDU, or simply 320 MHz (Max BW of EHT+ in case of EHT+).

Additionally, the bandwidth of the HE Sub-PPDU and the EHT (or EHT+) Sub-PPDU may always be set to 160 MHz, respectively, regardless of the transmitted BW. For example, assuming that the HE Sub-PPDU is transmitted in the primary 80 MHz and the EHT (or EHT+) Sub-PPDU is transmitted in the low 80 MHz of the secondary 160 MHz, the bandwidth of each PPDU may be simply set to 160 MHz even though each PPDU is being transmitted in the BW of 80 MHz.

<Non-AP STA Operation>

It is assumed that the HE PPDU is transmitted within the primary 160 MHz, and it is assumed that the EHT PPDU is transmitted within the secondary 160 MHz. Each transmission bandwidth may be 160 MHz or less (eg, 80 MHz). In addition, the A-PPDU described above assumes a downlink (DL) A-PPDU, the HE PPDU may be a SU/MU PPDU and the EHT PPDU may be an MU PPDU. It is assumed that the BW field in each sub-PPDU is indicated only by the BW in which each sub-field is transmitted. The bandwidth of the EHT PPDU may be indicated as 320 MHz in consideration of the BW of the entire A-PPDU, but an error may occur during decoding of the OBSS STA, so the BW of the entire A-PPDU is not considered.

In this situation, Non-AP STAs may receive the A-PPDU by the following operation.

i) If SST is not considered, all non-AP HE/EHT STAs may be sensing Primary 20/40/80/160/320 MHz according to their operation BW. At this time, when the A-PPDU is transmitted, the non-AP HE STAs perform decoding only within the primary 160 MHz and only the HE PPDU is transmitted within the primary 160 MHz. According to the indicator of the bandwidth in which the HE PPDU is transmitted, decoding can be performed only within the corresponding channel to receive its own data. If data is transmitted from the HE PPDU among the non-AP EHT STAs, the PPDU can be received without any problem like the non-AP HE STA. However, when the operating capability of the non-AP EHT STA is 160 MHz, it is necessary to decode by switching from the primary 160 MHz to the secondary 160 MHz through specific signaling. If data is transmitted from the EHT PPDU among non-AP EHT STAs, the PPDU may be received by switching to the secondary 160 MHz through specific signaling or performing decoding within the secondary 160 MHz. Specific signaling may be indicated through a specific reserved field in the HE PPDU. Even if the operating capability of the non-AP EHT STA is 320 MHz, the primary 160 MHz side is usually decoded in the original implementation, but here it is designated to decode the secondary 160 MHz. That is, according to the bandwidth indicator through which the EHT PPDU is transmitted, decoding can be performed only within the corresponding channel to receive its own data.

ii) When SST is considered, non-AP HE STAs may be allocated to a specific 80 MHz within the primary 160 MHz, and non-AP EHT STAs may be allocated to any 80 MHz channel within 320 MHz. However, the non-AP EHT STA allocated in the primary 160 MHz receives data through the HE PPDU, and the non-AP EHT STA allocated in the secondary 160 MHz receives data through the EHT PPDU. That is, each non-AP STA may receive data by performing decoding only within a channel allocated to it by the SST during a specific service period (TWT SP).

In addition, in the present specification, when the aggregated PPDU is configured of HE and EHT PPDUs, a scheme for configuring STF and LTF in each sub-PPDU is proposed.

2.3 Method for Configuring STF and LTF in A-PPDU

2.3.1. Consists of 80 MHz STF and LTF Sequences for Each 80 MHz

The simplest way. For example, in FIG. 12 , if Sub-PPDU-3 is an HE PPDU and Sub-PPDU-2 and Sub-PPDU-1 are EHT-PPDUs, HE-STF and HE-LTF of Sub-PPDU-3 consist of 80 MHz HE-STF and 80 MHz HE-LTF, EHT-STF and EHT-LTF of each 80 MHz channel of Sub-PPDU-2 and Sub-PPDU-1 consist of an 80 MHz EHT-STF sequence and an 80 MHz EHT-LTF sequence. Sub-PPDU-1 has a bandwidth of 160 MHz, but consists of an 80 MHz EHT-STF sequence and an 80 MHz EHT-LTF sequence for each 80 MHz. This is easy to implement, but may be undesirable from a PAPR standpoint.

2.3.2. Consists of STF and LTF Sequence Corresponding to BW Indicated in Sub-PPDU

Each field may be configured with a HE/EHT-STF/LTF sequence corresponding to the BW indicated in each Sub-PPDU. For example, in FIG. 12 , it is assumed that Sub-PPDU-3 is an HE PPDU, BW of Sub-PPDU-3 is set to 80 MHz, Sub-PPDU-2 and Sub-PPDU-1 are EHT-PPDU, and BWs of the Sub-PPDU-2 and Sub-PPDU-1 are 80 MHz and 160 MHz, respectively. Then, the HE-STF and HE-LTF of Sub-PPDU-3 are configured of an 80 MHz HE-STF sequence and an 80 MHz HE-LTF sequence, EHT-STF and EHT-LTF of Sub-PPDU-2 are configured of an 80 MHz EHT-STF sequence and an 80 MHz EHT-LTF sequence. EHT-STF and EHT-LTF of Sub-PPDU-1 are configured of a 160 MHz EHT-STF sequence and a 160 MHz EHT-LTF sequence.

As another example, in FIG. 12 , it is assumed that Sub-PPDU-3 is an HE PPDU, BW of Sub-PPDU-3 is set to 80 MHz, Sub-PPDU-2 and Sub-PPDU-1 are EHT-PPDU, and BWs of the Sub-PPDU-2 and Sub-PPDU-1 are 240 MHz (or 320 MHz with 80 MHz punctured), respectively. Then, the HE-STF and HE-LTF of Sub-PPDU-3 are configured of an 80 MHz HE-STF sequence and an 80 MHz HE-LTF sequence, EHT-STF and EHT-LTF of Sub-PPDU-2 and Sub-PPDU-1 are configured using a 240 MHz EHT-STF and a 240 MHz EHT-LTF (or configured using 320 MHz EHT-STF and 320 MHz EHT-LTF). At this time, the sequence in each Sub-PPDU consists of a 240 MHz EHT-STF sequence and a 240 MHz EHT-LTF sequence corresponding to the frequency position of each Sub-PPDU (Or it is configured of 320 MHz EHT-STF and 320 MHz EHT-LTF corresponding to the frequency position of each Sub-PPDU).

This may be easy to implement by configuring the STF and LTF sequences according to the BW, but the PAPR problem may remain. However, it may be preferable in consideration of decoding of an OBSS STA or STAs that do not participate in transmission.

2.3.3. Consists of STF and LTF Sequences Corresponding to the Total BW of the Same Version Sub-PPDUs

Regardless of the BW indicator of each Sub-PPDU, it can be configured of STF and LTF sequences corresponding to the total BW of the same version Sub-PPDUs. For example, in FIG. 12 , if Sub-PPDU-3 is an HE PPDU and Sub-PPDU-2 and Sub-PPDU-1 are EHT-PPDUs, HE-STF and HE-LTF of Sub-PPDU-3 consist of an 80 MHz HE-STF sequence and an 80 MHz HE-LTF sequence regardless of the BW indicator, EHT-STF and EHT-LTF of Sub-PPDU-2 and Sub-PPDU-1 are configured using 240 MHz EHT-STF and 240 MHz EHT-LTF (or configured using 320 MHz EHT-STF and 320 MHz EHT-LTF). At this time, the sequence in each Sub-PPDU consists of a 240 MHz EHT-STF sequence and a 240 MHz EHT-LTF sequence corresponding to the frequency position of each Sub-PPDU (Or it is configured of 320 MHz EHT-STF and 320 MHz EHT-LTF corresponding to the frequency position of each Sub-PPDU).

This can be complex in implementation, but it can be effective in reducing PAPR even a little. It may be desirable in consideration of decoding of OBSS STAs or STAs that do not participate in transmission.

2.3.4. Sub-PPDU for EHT STA (or EHT+STA) is Composed of STF and LTF Sequence Corresponding to the Entire BW of the Aggregated PPDU.

A Sub-PPDU for an EHT (or EHT+) STA consists of an STF and an LTF sequence corresponding to the entire BW of the aggregated PPDU regardless of the BW indicator. For example, in FIG. 12 , if Sub-PPDU-3 is an HE PPDU and Sub-PPDU-2 and Sub-PPDU-1 are EHT-PPDUs, Regardless of the BW indicator, HE-STF and HE-LTF of Sub-PPDU-3 consist of an 80 MHz HE-STF sequence and an 80 MHz HE-LTF sequence. EHT-STF and EHT-LTF of Sub-PPDU-2 and Sub-PPDU-1 are configured using 320 MHz EHT-STF and 320 MHz EHT-LTF. At this time, the sequence in each Sub-PPDU is configured of a 320 MHz EHT-STF sequence and a 320 MHz EHT-LTF sequence corresponding to the frequency position of each Sub-PPDU.

This can be complex in implementation, but it can be effective in reducing PAPR. However, if the OBSS STA has wide bandwidth capability, decoding may be performed by combining the entire A-PPDU according to the BW indicator, and in this case, a decoding error may occur due to different contents of each sub PPDU.

2.3.5. Fixed Sequence

The sequence of the Sub-PPDU for the HE STA may always be configured based on the 160 MHz sequence, and the sequence of the Sub-PPDU for the EHT STA may always be configured based on the 320 MHz sequence (EHT+ is configured based on the sequence defined in the maximum BW) That is, the sequence of each 80 MHz HE/EHT Sub-PPDU is configured of a sequence corresponding to the frequency position of each 160 MHz/320 MHz channel. For example, if the HE Sub-PPDU is located at 80 MHz high among 160 MHz channels, the sequence corresponding to the high 80 MHz among 160 MHz HE sequences is also applied to the sub-PPDU. As another example, if it is located in the second 80 MHz of the 320 MHz channel of the EHT Sub-PPDU, the sequence corresponding to the second 80 MHz of the 320 MHz sequence is applied to the Sub-PPDU. The BW indicator can also be fixed in this way, and it can be the simplest sequence configuration method.

2.3.6. If SST is Considered

A case in which SST is considered may be additionally considered. Considering the SST, the HE STA may be located at any 80 MHz within the primary 160 MHz (i.e., the primary 80 MHz or the secondary 80 MHz), and the EHT STA may be located at any 80 MHz within the 320 MHz channel. In addition, the EHT+STA may be located at any 80 MHz within the maximum possible BW channel of the EHT+. For example, the HE STA may be located in the secondary 80 MHz and the EHT STA may be located in the primary 80 MHz. When the HE STA is located at the primary 80 MHz, the sequence of the Sub-PPDU for the HE may be configured based on the 80 MHz or 160 MHz sequence according to the methods of 2.3.1 to 2.3.5 above.

When the HE STA is located in the secondary 80 MHz, the sequence of the Sub-PPDU for the HE may always be configured based on the 160 MHz sequence. That is, a sequence corresponding to a secondary 80 MHz channel position among the 160 MHz sequence may be applied to the Sub-PPDU. If the EHT (or EHT+) STA is located only at the primary 80 MHz, the sequence of the Sub-PPDU for this purpose may be configured based on the sequence of 80 MHz or full BW (160 MHz) or 320 MHz (in EHT+, the maximum BW of EHT+) as in the method of 2.3.1˜2.3.5. If EHT (or EHT+) STA is located only at secondary 160 MHz, Sub-PPDU for this purpose may be configured based on the sequence of 160 MHz or full BW (indicating 240 MHz or 320 MHz and additional puncturing indicators can be considered) or 320 MHz (in the case of EHT+, the maximum BW of EHT+) as in the method of 2.3.1˜2.3.5. If the EHT (or EHT+) STA is located at primary 80 MHz and secondary 160 MHz, Sub-PPDU for this purpose can be configured based on the sequence of the entire BW (indicating 320 MHz and additional puncturing indicator can be considered) or 320 MHz (in case of EHT+, the maximum BW of EHT+) as in the method of 2.3.1˜2.3.5.

2.3.7. In Case of Limiting Only HE Sub-PPDU within Primary 160 MHz

When an 802.11ax STA capable of a specific 160 MHz detects a signal in the entire 160 MHz channel, decoding may be performed by combining L-SIG and HE-SIG-A. In this case, if the HE Sub-PPDU and the EHT Sub-PPDU are mixed within the primary 160 MHz, decoding problems may occur in such terminals. Therefore, when configuring the A-PPDU, the EHT Sub-PPDU can always exist only in the Secondary 160 MHz, and it can be limited to the existence of only the HE Sub-PPDU in the Primary 160 MHz. In such a situation, sequence application can be considered, and the methods proposed above can be applied as they are. That is, in the HE Sub-PPDU, an HE sequence corresponding to 80 MHz or 160 MHz or actually used BW or indicated BW may be applied according to the location of each Sub-PPDU channel. In the EHT Sub-PPDU, an EHT sequence corresponding to 80 MHz or actually used BW or the indicated BW or the entire BW of the A-PPDU or simply 320 MHz may be applied according to the location of each Sub-PPDU channel.

Additionally, regardless of the BW and the indicated BW used for the HE Sub-PPDU and the EHT Sub-PPDU, the 160 MHz HE sequence and the 160 MHz EHT sequence may always be applied according to the location of each Sub-PPDU. For example, assuming that HE Sub-PPDU is transmitted in primary 80 MHz and EHT Sub-PPDU is transmitted in low 80 MHz of secondary 160 MHz, even though each is transmitted with BW of 80 MHz (the indicated BW can be defined in various ways), it can be applied to the location of each Sub-PPDU simply by using the 160 MHz HE sequence and the 160 MHz EHT sequence.

<Non-AP STA Operation>

It is assumed that the HE PPDU is transmitted within the primary 160 MHz and the EHT PPDU is transmitted within the secondary 160 MHz. Each transmission bandwidth may be less than 160 MHz (e.g. 80 MHz). Also, assuming that the above-described A-PPDU is a DL A-PPDU, the HE PPDU may be a SU/MU PPDU and the EHT PPDU may be an MU PPDU. It is assumed that the BW field in each sub-PPDU is indicated only by the BW in which each sub-field is transmitted. The EHT PPDU may be indicated at 320 MHz in consideration of the BW of the entire A-PPDU, but since an error may occur during decoding of the OBSS STA, the BW of the entire A-PPDU is not considered. In addition, the STF/LTF sequence assumes that a sequence corresponding to the indicated BW is used for each Sub-PPDU. This may be desirable in consideration of decoding of OBSS STAs or STAs not participating in transmission.

In this situation, Non-AP STAs may receive the A-PPDU by the following operation.

i) If SST is not considered, all non-AP HE/EHT STAs may sense Primary 20/40/80/160/320 MHz according to their operating BW. At this time, when the A-PPDU is transmitted, the non-AP HE STAs perform decoding only within the primary 160 MHz and since only the HE PPDU is transmitted within the primary 160 MHz, the PPDU can be received in the same manner as before without a switching issue. According to the bandwidth indicator in which the HE PPDU is transmitted, decoding can be performed using the STF/LTF sequence corresponding to the BW in the corresponding channel to receive its own data. If data is transmitted from the HE PPDU among the non-AP EHT STAs, the PPDU can be received without any problem like the non-AP HE STA. However, when the operating capability of the non-AP EHT STA is 160 MHz, it is necessary to decode by switching from the primary 160 MHz to the secondary 160 MHz through specific signaling. If data is transmitted from the EHT PPDU among non-AP EHT STAs, the PPDU may be received by switching to the secondary 160 MHz through specific signaling or performing decoding within the secondary 160 MHz. Specific signaling may be indicated through a specific reserved field in the HE PPDU. Even if the operating capability of the non-AP EHT STA is 320 MHz, the primary 160 MHz side is usually decoded in the original implementation, but here it is designated to decode the secondary 160 MHz. That is, according to the bandwidth indicator through which the EHT PPDU is transmitted, decoding can be performed using the STF/LTF sequence corresponding to the BW in the corresponding channel to receive its own data.

ii) When SST is considered, non-AP HE STAs may be allocated to a specific 80 MHz within the primary 160 MHz, and non-AP EHT STAs may be allocated to any 80 MHz channel within 320 MHz. However, the non-AP EHT STA allocated in the primary 160 MHz receives data through the HE PPDU, and the non-AP EHT STA allocated in the secondary 160 MHz receives data through the EHT PPDU. That is, each non-AP STA may receive data by performing decoding using the STF/LTF sequence corresponding to the BW in the channel allocated to it by the SST during a specific service period (TWT SP).

FIG. 14 is a flowchart illustrating the operation of the transmitting apparatus/device according to the present embodiment.

The above-described STF sequence (i.e., EHT-STF/EHTS sequence) may be transmitted according to the example of FIG. 14 .

The example of FIG. 14 may be performed by a transmitting device (AP and/or non-AP STA).

Some of each step (or detailed sub-step to be described later) of the example of FIG. 14 may be skipped/omitted.

In step S100, the transmitting device may obtain control information for the STF sequence. For example, the transmitting device may obtain information related to a bandwidth (e.g., 80/160/240/320 MHz) applied to the STF sequence. Additionally/alternatively, the transmitting device may obtain information related to a characteristic applied to the STF sequence (e.g., information indicating generation of a 1×, 2×, or 4× sequence).

In step S200, the transmitting device may configure or generate a control signal/field (e.g., EHT-STF signal/field) based on the obtained control information (e.g., information related to the bandwidth).

The step S200 may include a more specific sub-step.

For example, step S200 may further include selecting one STF sequence from among a plurality of STF sequences based on the control information obtained through the step S100.

Additionally/alternatively, step S200 may further include performing a power boosting.

Step S200 may also be referred to as a step of generating a sequence.

In step S300, the transmitting device may transmit a signal/field/sequence configured in the step S200 to the receiving apparatus/device based on the step S300.

The step S200 may include a more specific sub-step.

For example, the transmitting apparatus/device may perform a phase rotation step. Specifically, the transmitting apparatus/device may perform the phase rotation step in units of 20 MHz*N (N=integer) for the sequence generated through the step S200.

Additionally/alternatively, the transmitting apparatus/device may perform at least one of CSD, Spatial Mapping, IDFT/IFFT operation, GI insertion, and the like.

A signal/field/sequence constructed according to the present specification may be transmitted in the form of FIG. 10 .

An example of FIG. 14 relates to an example of a transmitting apparatus/device (AP and/or non-AP STA).

As shown in FIG. 1 , the transmitting apparatus/device may include a memory 112, a processor 111, and a transceiver 113.

The memory 112 may store information related to a plurality of STF sequences described herein. In addition, it may store control information for generating an STF sequence/PPDU.

The processor 111 may generate various sequences (e.g., STF sequences) based on the information stored in the memory 112 and configure the PPDU. An example of the PPDU generated by the processor 111 may be as shown in FIG. 10 .

The processor 111 may perform some of the operations illustrated in FIG. 14 . For example, it is possible to obtain control information for generating an STF sequence and configure the STF sequence.

For example, the processor 111 may include an additional sub-unit. A detailed unit included in the processor 111 may be configured as shown in FIG. 11 . That is, as shown, the processor 111 may perform operations such as CSD, spatial mapping, IDFT/IFFT operation, and GI insertion.

The illustrated transceiver 113 may include an antenna and may perform analog signal processing. Specifically, the processor 111 may control the transceiver 113 to transmit the PPDU generated by the processor 111.

FIG. 15 is a flowchart illustrating the operation of the receiving apparatus/device according to the present embodiment.

The above-described STF sequence (i.e., EHT-STF/EHTS sequence) may be transmitted according to the example of FIG. 15 .

The example of FIG. 15 may be performed by a receiving apparatus/device (AP and/or non-AP STA).

Some of each step (or detailed sub-step to be described later) of the example of FIG. 15 may be skipped/omitted.

In step S400, the receiving apparatus/device may receive a signal/field including an STF sequence (i.e., an EHT-STF/EHTS sequence) in step S400. The received signal may be in the form of FIG. 10 .

The sub-step of step S400 may be determined based on the step S300. That is, in the step S400, an operation for restoring the results of the phase rotation CSD, spatial mapping, IDFT/IFFT operation, and GI insert operation applied in step S300 may be performed.

In step S400, the STF sequence may perform various functions, such as detecting time/frequency synchronization of a signal or estimating an AGC gain.

In step S500, the receiving apparatus/device may perform decoding on the received signal based on the STF sequence.

For example, step S500 may include decoding the data field of the PPDU including the STF sequence. That is, the receiving apparatus/device may decode a signal included in the data field of the successfully received PPDU based on the STF sequence.

In step S600, the receiving apparatus/device may process the data decoded in step S2320.

For example, the receiving apparatus/device may perform a processing operation of transferring the decoded data to a higher layer (e.g., MAC layer) in step S500. In addition, when generation of a signal is instructed from the upper layer to the PHY layer in response to data transferred to the upper layer, a subsequent operation may be performed.

The example of FIG. 15 relates to an example of a transmitting apparatus/device (AP and/or non-AP STA).

As shown in FIG. 1 , the transmitting apparatus/device may include a memory 112, a processor 111, and a transceiver 113.

The memory 112 may store information related to a plurality of STF sequences described herein. In addition, it may store control information for generating an STF sequence/PPDU.

The processor 111 may generate various sequences (e.g., STF sequences) based on the information stored in the memory 112 and configure the PPDU. An example of the PPDU generated by the processor 111 may be as shown in FIG. 10 .

The processor 111 may perform some of the operations illustrated in FIG. 15 . For example, it is possible to obtain control information for generating an STF sequence and configure the STF sequence.

For example, the processor 111 may include an additional sub-unit. A detailed unit included in the processor 111 may be configured as shown in FIG. 11 . That is, as shown, the processor 111 may perform operations such as CSD, spatial mapping, IDFT/IFFT operation, and GI insertion.

The illustrated transceiver 113 may include an antenna and may perform analog signal processing. Specifically, the processor 111 may control the transceiver 113 to transmit the PPDU generated by the processor 111.

Some technical features shown in FIG. 15 may be implemented by the transceiver 113. The analog RF processing shown in detail may be included in the transceiver 113.

Hereinafter, the above-described embodiment will be described with reference to FIGS. 1 to 15 .

FIG. 16 is a flowchart illustrating a procedure in which a transmitting STA transmits an A-PPDU according to the present embodiment.

The example of FIG. 16 may be performed in a network environment in which a next-generation wireless LAN system (IEEE 802.11be or EHT wireless LAN system) is supported. The next-generation wireless LAN system is a wireless LAN system improved from the 802.11ax system, and may support backward compatibility with the 802.11ax system.

The example of FIG. 16 is performed by a transmitting STA, and the transmitting STA may correspond to an access point (AP). The receiving STA of FIG. 16 may correspond to an STA supporting an Extremely High Throughput (EHT) WLAN system.

This embodiment proposes a method of configuring an A-PPDU in which an HE PPDU and an EHT PPDU are simultaneously transmitted. In addition, this embodiment proposes a method of indicating the bandwidth of each sub-PPDU in the A-PPDU and a method of setting an STF/LTF sequence in each sub-PPDU.

In step S1610, the transmitting STA generates an Aggregated-Physical Protocol Data Unit (A-PPDU).

In step S1620, the transmitting STA transmits the A-PPDU to a receiving STA.

The A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel. The first PPDU is a PPDU supporting a High Efficiency (HE) WLAN system, and the second PPDU is a PPDU supporting an Extremely High Throughput (EHT) WLAN system. That is, the HE PPDU and the EHT PPDU may be aggregated with each other in the frequency domain and transmitted simultaneously through the A-PPDU. Since the bandwidth that the HE WLAN system can support is 160 MHz, it is preferable that the HE PPDU is configured in the primary 160 MHz channel and the EHT PPDU is configured in the secondary 160 MHz channel.

The first PPDU includes a first indicator including information on the bandwidth of the first PPDU. The second PPDU includes a second indicator including information on the bandwidth of the second PPDU.

The bandwidth of the first PPDU may be set to 80 MHz or 160 MHz based on the first indicator. The bandwidth of the second PPDU may be set to 80 MHz, 160 MHz, or 320 MHz based on the second indicator. It is assumed that the first and second indicators indicate a bandwidth of at least 80 MHz. The bandwidths of the first and second PPDUs may be set in consideration of not only the first and second indicators but also a preamble puncturing indicator.

The first PPDU may include a first Short Training Field (STF) and a first Long Training Field (LTF). The second PPDU includes a second STF and a second LTF.

If the bandwidth of the first PPDU is 80 MHz, the first STF may include a HE-STF sequence for an 80 MHz band, and the first LTF may include a HE-LTF sequence for an 80 MHz band. If the bandwidth of the first PPDU is 160 MHz, the first STF may include a HE-STF sequence for a 160 MHz band, and the first LTF may include a HE-LTF sequence for a 160 MHz band. That is, the sequence of the first STF and the first LTF may be set according to the bandwidth of the first PPDU indicated by the first indicator.

In addition, when the bandwidth of the second PPDU is 80 MHz, the second STF may include an EHT-STF sequence for an 80 MHz band, and the second LTF may include an EHT-LTF sequence for an 80 MHz band. If the bandwidth of the second PPDU is 160 MHz, the second STF may include an EHT-STF sequence for a 160 MHz band, and the second LTF may include an EHT-LTF sequence for a 160 MHz band. If the bandwidth of the second PPDU is 320 MHz, the second STF includes an EHT-STF sequence located in the secondary 160 MHz channel among EHT-STF sequences for the 320 MHz band, the second LTF may include an EHT-LTF sequence located in the secondary 160 MHz channel among the EHT-LTF sequences for the 320 MHz band (set as a sequence corresponding to the frequency domain). Similarly, the sequence of the second STF and the second LTF may be configured according to the bandwidth of the second PPDU indicated by the second indicator.

Hereinafter, a decoding process of the receiving STA according to whether the SST is operated will be described.

First, it is assumed that the transmitting STA and the receiving STA do not support Subchannel Selective Transmission (SST). In this case, it is assumed that the operable band of the receiving STA is 160 MHz, and the receiving STA is a non-AP EHT STA capable of decoding the second PPDU. In this case, the receiving STA needs to implement a decoding operation by switching from a primary 160 MHz channel to a secondary 160 MHz channel in order to decode the second PPDU. Even if the operable band of the receiving STA is 320 MHz, in implementation, the receiving STA tends to decode the primary 160 MHz channel. Similarly, the receiving STA needs to implement a decoding operation by switching from the primary 160 MHz channel to the secondary 160 MHz channel in order to decode the second PPDU.

Specifically, the receiving STA may receive the first signaling information from the transmitting STA. The receiving STA may decode the second PPDU in the secondary 160 MHz channel based on the first signaling information.

The first signaling information may include information for switching a decoding channel of the receiving STA from the primary 160 MHz channel to the secondary 160 MHz channel. The first signaling information may be included in a reserved field of the first PPDU. That is, the first signaling information may be transmitted through the primary 160 MHz channel.

when the transmitting STA and the receiving STA support SST, the receiving STA may obtain information on a Target Wake Time Service Period (TWT SP) after negotiation for the SST. The receiving STA may decode the second PPDU in a channel allocated during the TWT SP. The channel allocated during the TWT SP may be the secondary 160 MHz channel. That is, the transmitting STA and the receiving STA may access a specific subchannel (or secondary channel) during the TWT SP and use only the corresponding channel.

The first PPDU may include a first legacy field, a first control field, and a data field. The first legacy field may include a Legacy-Short Training Field (L-STF), a Legacy-Long Training Field (L-LTF), and a Legacy-Signal (L-SIG). The first control field may include HE-SIG (including HE-SIG-A or HE-SIG-B), HE-STF, and HE-LTF.

The second PPDU may include a second legacy field, a second control field, and a data field. The second legacy field may include L-STF, L-LTF, L-SIG and RL-SIG. The second control field may include Universal-Signal (U-SIG), EHT-SIG, EHT-STF, and EHT-LTF.

The first indicator may be included in a bandwidth (BW) field of the HE-SIG-A field of the first PPDU. The second indicator may be included in a version independent field of the U-SIG of the second PPDU.

FIG. 17 is a flowchart illustrating a procedure in which a receiving STA receives a PPDU according to the present embodiment.

The example of FIG. 17 may be performed in a network environment in which a next-generation wireless LAN system (IEEE 802.11be or EHT wireless LAN system) is supported. The next-generation wireless LAN system is a wireless LAN system improved from the 802.11ax system, and may support backward compatibility with the 802.11ax system.

The example of FIG. 17 is performed by the receiving STA and may correspond to a STA supporting an Extremely High Throughput (EHT) WLAN system. The transmitting STA of FIG. 17 may correspond to an access point (AP).

This embodiment proposes a method of configuring an A-PPDU in which an HE PPDU and an EHT PPDU are simultaneously transmitted. In addition, this embodiment proposes a method of indicating the bandwidth of each sub-PPDU in the A-PPDU and a method of setting an STF/LTF sequence in each sub-PPDU.

In step S1710, the receiving station (STA) receives an Aggregated-Physical Protocol Data Unit (A-PPDU) from a transmitting STA.

In step S1720, the receiving STA decodes the A-PPDU.

The A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel. The first PPDU is a PPDU supporting a High Efficiency (HE) WLAN system, and the second PPDU is a PPDU supporting an Extremely High Throughput (EHT) WLAN system. That is, the HE PPDU and the EHT PPDU may be aggregated with each other in the frequency domain and transmitted simultaneously through the A-PPDU. Since the bandwidth that the HE WLAN system can support is 160 MHz, it is preferable that the HE PPDU is configured in the primary 160 MHz channel and the EHT PPDU is configured in the secondary 160 MHz channel.

The first PPDU includes a first indicator including information on the bandwidth of the first PPDU. The second PPDU includes a second indicator including information on the bandwidth of the second PPDU.

The bandwidth of the first PPDU may be set to 80 MHz or 160 MHz based on the first indicator. The bandwidth of the second PPDU may be set to 80 MHz, 160 MHz, or 320 MHz based on the second indicator. It is assumed that the first and second indicators indicate a bandwidth of at least 80 MHz. The bandwidths of the first and second PPDUs may be set in consideration of not only the first and second indicators but also a preamble puncturing indicator.

The first PPDU may include a first Short Training Field (STF) and a first Long Training Field (LTF). The second PPDU includes a second STF and a second LTF.

If the bandwidth of the first PPDU is 80 MHz, the first STF may include a HE-STF sequence for an 80 MHz band, and the first LTF may include a HE-LTF sequence for an 80 MHz band. If the bandwidth of the first PPDU is 160 MHz, the first STF may include a HE-STF sequence for a 160 MHz band, and the first LTF may include a HE-LTF sequence for a 160 MHz band. That is, the sequence of the first STF and the first LTF may be set according to the bandwidth of the first PPDU indicated by the first indicator.

In addition, when the bandwidth of the second PPDU is 80 MHz, the second STF may include an EHT-STF sequence for an 80 MHz band, and the second LTF may include an EHT-LTF sequence for an 80 MHz band. If the bandwidth of the second PPDU is 160 MHz, the second STF may include an EHT-STF sequence for a 160 MHz band, and the second LTF may include an EHT-LTF sequence for a 160 MHz band. If the bandwidth of the second PPDU is 320 MHz, the second STF includes an EHT-STF sequence located in the secondary 160 MHz channel among EHT-STF sequences for the 320 MHz band, the second LTF may include an EHT-LTF sequence located in the secondary 160 MHz channel among the EHT-LTF sequences for the 320 MHz band (set as a sequence corresponding to the frequency domain). Similarly, the sequence of the second STF and the second LTF may be configured according to the bandwidth of the second PPDU indicated by the second indicator.

Hereinafter, a decoding process of the receiving STA according to whether the SST is operated will be described.

First, it is assumed that the transmitting STA and the receiving STA do not support Subchannel Selective Transmission (SST). In this case, it is assumed that the operable band of the receiving STA is 160 MHz, and the receiving STA is a non-AP EHT STA capable of decoding the second PPDU. In this case, the receiving STA needs to implement a decoding operation by switching from a primary 160 MHz channel to a secondary 160 MHz channel in order to decode the second PPDU. Even if the operable band of the receiving STA is 320 MHz, in implementation, the receiving STA tends to decode the primary 160 MHz channel. Similarly, the receiving STA needs to implement a decoding operation by switching from the primary 160 MHz channel to the secondary 160 MHz channel in order to decode the second PPDU.

Specifically, the receiving STA may receive the first signaling information from the transmitting STA. The receiving STA may decode the second PPDU in the secondary 160 MHz channel based on the first signaling information.

The first signaling information may include information for switching a decoding channel of the receiving STA from the primary 160 MHz channel to the secondary 160 MHz channel. The first signaling information may be included in a reserved field of the first PPDU. That is, the first signaling information may be transmitted through the primary 160 MHz channel.

when the transmitting STA and the receiving STA support SST, the receiving STA may obtain information on a Target Wake Time Service Period (TWT SP) after negotiation for the SST. The receiving STA may decode the second PPDU in a channel allocated during the TWT SP. The channel allocated during the TWT SP may be the secondary 160 MHz channel. That is, the transmitting STA and the receiving STA may access a specific subchannel (or secondary channel) during the TWT SP and use only the corresponding channel.

The first PPDU may include a first legacy field, a first control field, and a data field. The first legacy field may include a Legacy-Short Training Field (L-STF), a Legacy-Long Training Field (L-LTF), and a Legacy-Signal (L-SIG). The first control field may include HE-SIG (including HE-SIG-A or HE-SIG-B), HE-STF, and HE-LTF.

The second PPDU may include a second legacy field, a second control field, and a data field. The second legacy field may include L-STF, L-LTF, L-SIG and RL-SIG. The second control field may include Universal-Signal (U-SIG), EHT-SIG, EHT-STF, and EHT-LTF.

The first indicator may be included in a bandwidth (BW) field of the HE-SIG-A field of the first PPDU. The second indicator may be included in a version independent field of the U-SIG of the second PPDU.

3. Apparatus/Device Configuration

The technical features of the present specification described above may be applied to various devices and methods. For example, the above-described technical features of the present specification may be performed/supported through the apparatus of FIGS. 1 and/or 11 . For example, the above-described technical features of the present specification may be applied only to a part of FIGS. 1 and/or 11 . For example, the technical features of the present specification described above are implemented based on the processing chips 114 and 124 of FIG. 1 , or implemented based on the processors 111 and 121 and the memories 112 and 122 of FIG. 1 , or, may be implemented based on the processor 610 and the memory 620 of FIG. 11 For example, the apparatus of the present specification may receive an A-PPDU from a transmitting STA; and decodes the A-PPDU.

The technical features of the present specification may be implemented based on a CRM (computer readable medium). For example, CRM proposed by the present specification is at least one computer readable medium including at least one computer readable medium including instructions based on being executed by at least one processor.

The CRM may store instruction that perform operations comprising receiving an A-PPDU from a transmitting STA; and decoding the A-PPDU. The instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to CRM in the present specification may be the processor(s) 111 and/or 121 or the processing chip(s) 114 and/or 124 of FIG. 1 , or the processor 610 of FIG. 11 . Meanwhile, the CRM of the present specification may be the memory(s) 112 and/or 122 of FIG. 1 , the memory 620 of FIG. 11 , or a separate external memory/storage medium/disk.

The foregoing technical features of this specification are applicable to various applications or business models. For example, the foregoing technical features may be applied for wireless communication of a device supporting artificial intelligence (AI).

Artificial intelligence refers to a field of study on artificial intelligence or methodologies for creating artificial intelligence, and machine learning refers to a field of study on methodologies for defining and solving various issues in the area of artificial intelligence. Machine learning is also defined as an algorithm for improving the performance of an operation through steady experiences of the operation.

An artificial neural network (ANN) is a model used in machine learning and may refer to an overall problem-solving model that includes artificial neurons (nodes) forming a network by combining synapses. The artificial neural network may be defined by a pattern of connection between neurons of different layers, a learning process of updating a model parameter, and an activation function generating an output value.

The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses that connect neurons. In the artificial neural network, each neuron may output a function value of an activation function of input signals input through a synapse, weights, and deviations.

A model parameter refers to a parameter determined through learning and includes a weight of synapse connection and a deviation of a neuron. A hyper-parameter refers to a parameter to be set before learning in a machine learning algorithm and includes a learning rate, the number of iterations, a mini-batch size, and an initialization function.

Learning an artificial neural network may be intended to determine a model parameter for minimizing a loss function. The loss function may be used as an index for determining an optimal model parameter in a process of learning the artificial neural network.

Machine learning may be classified into supervised learning, unsupervised learning, and reinforcement learning.

Supervised learning refers to a method of training an artificial neural network with a label given for training data, wherein the label may indicate a correct answer (or result value) that the artificial neural network needs to infer when the training data is input to the artificial neural network. Unsupervised learning may refer to a method of training an artificial neural network without a label given for training data. Reinforcement learning may refer to a training method for training an agent defined in an environment to choose an action or a sequence of actions to maximize a cumulative reward in each state.

Machine learning implemented with a deep neural network (DNN) including a plurality of hidden layers among artificial neural networks is referred to as deep learning, and deep learning is part of machine learning. Hereinafter, machine learning is construed as including deep learning.

The foregoing technical features may be applied to wireless communication of a robot.

Robots may refer to machinery that automatically process or operate a given task with own ability thereof. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation may be referred to as an intelligent robot.

Robots may be classified into industrial, medical, household, military robots and the like according uses or fields. A robot may include an actuator or a driver including a motor to perform various physical operations, such as moving a robot joint. In addition, a movable robot may include a wheel, a brake, a propeller, and the like in a driver to run on the ground or fly in the air through the driver.

The foregoing technical features may be applied to a device supporting extended reality.

Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphic technology of providing a real-world object and background only in a CG image, AR technology is a computer graphic technology of providing a virtual CG image on a real object image, and MR technology is a computer graphic technology of providing virtual objects mixed and combined with the real world.

MR technology is similar to AR technology in that a real object and a virtual object are displayed together. However, a virtual object is used as a supplement to a real object in AR technology, whereas a virtual object and a real object are used as equal statuses in MR technology.

XR technology may be applied to a head-mount display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop computer, a desktop computer, a TV, digital signage, and the like. A device to which XR technology is applied may be referred to as an XR device.

The claims recited in the present specification may be combined in a variety of ways. For example, the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method. In addition, the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method. 

1. A method in a Wireless Local Area Network (WLAN) system, the method comprising: receiving, by a receiving station (STA), an Aggregated-Physical Protocol Data Unit (A-PPDU) from a transmitting STA; and decoding, by the receiving STA, the A-PPDU, wherein the A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel, wherein the first PPDU includes a first indicator including information on the bandwidth of the first PPDU, wherein the second PPDU includes a second indicator including information on the bandwidth of the second PPDU, wherein the first PPDU is a PPDU supporting a High Efficiency (HE) WLAN system, and wherein the second PPDU is a PPDU supporting an Extremely High Throughput (EHT) WLAN system.
 2. The method of claim 1, wherein the bandwidth of the first PPDU is set to 80 MHz or 160 MHz based on the first indicator, wherein the bandwidth of the second PPDU is set to 80 MHz, 160 MHz or 320 MHz based on the second indicator.
 3. The method of claim 2, wherein the first PPDU includes a first Short Training Field (STF) and a first Long Training Field (LTF), wherein the second PPDU includes a second STF and a second LTF.
 4. The method of claim 3, wherein if the bandwidth of the first PPDU is 80 MHz, the first STF includes a HE-STF sequence for an 80 MHz band, and the first LTF includes a HE-LTF sequence for an 80 MHz band, wherein if the bandwidth of the first PPDU is 160 MHz, the first STF includes a HE-STF sequence for a 160 MHz band, and the first LTF includes a HE-LTF sequence for a 160 MHz band.
 5. The method of claim 3, wherein if the bandwidth of the second PPDU is 80 MHz, the second STF includes an EHT-STF sequence for an 80 MHz band, and the second LTF includes an EHT-LTF sequence for an 80 MHz band, wherein if the bandwidth of the second PPDU is 160 MHz, the second STF includes an EHT-STF sequence for a 160 MHz band, and the second LTF includes an EHT-LTF sequence for a 160 MHz band, wherein if the bandwidth of the second PPDU is 320 MHz, the second STF includes an EHT-STF sequence located in the secondary 160 MHz channel among an EHT-STF sequence for a 320 MHz band, and the second LTF includes an EHT-LTF sequence located in the secondary 160 MHz channel among an EHT-LTF sequences for a 320 MHz band.
 6. The method of claim 1, wherein when the transmitting STA and the receiving STA do not support Subchannel Selective Transmission (SST) and the operable band of the receiving STA is 160 MHz, further comprising: receiving, by the receiving STA, first signaling information from the transmitting STA; and decoding, by the receiving STA, the second PPDU in the secondary 160 MHz channel based on the first signaling information, wherein the first signaling information includes information for switching a decoding channel of the receiving STA from the primary 160 MHz channel to the secondary 160 MHz channel, wherein the first signaling information is included in a reserved field of the first PPDU.
 7. The method of claim 1, wherein when the transmitting STA and the receiving STA support SST, further comprising: obtaining, by the receiving STA, information on a Target Wake Time Service Period (TWT SP) after negotiation for the SST; and decoding, by the receiving STA, the second PPDU in a channel allocated during the TWT SP, wherein the channel allocated during the TWT SP is the secondary 160 MHz channel.
 8. A receiving station (STA) in a Wireless Local Area Network (WLAN) system, the receiving STA comprising: a memory; a transceiver; and a processor operatively coupled to the memory and transceiver, wherein processor is configured to: receive an Aggregated-Physical Protocol Data Unit (A-PPDU) from a transmitting STA; and decode the A-PPDU, wherein the A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel, wherein the first PPDU includes a first indicator including information on the bandwidth of the first PPDU, wherein the second PPDU includes a second indicator including information on the bandwidth of the second PPDU, wherein the first PPDU is a PPDU supporting a High Efficiency (HE) WLAN system, and wherein the second PPDU is a PPDU supporting an Extremely High Throughput (EHT) WLAN system.
 9. A method in a Wireless Local Area Network (WLAN) system, the method comprising: generating, by a transmitting station (STA), an Aggregated-Physical Protocol Data Unit (A-PPDU); and transmitting, by the transmitting STA, the A-PPDU to a receiving STA, wherein the A-PPDU includes a first PPDU for a primary 160 MHz channel and a second PPDU for a secondary 160 MHz channel, wherein the first PPDU includes a first indicator including information on the bandwidth of the first PPDU, wherein the second PPDU includes a second indicator including information on the bandwidth of the second PPDU, wherein the first PPDU is a PPDU supporting a High Efficiency (HE) WLAN system, and wherein the second PPDU is a PPDU supporting an Extremely High Throughput (EHT) WLAN system.
 10. The method of claim 9, wherein the bandwidth of the first PPDU is set to 80 MHz or 160 MHz based on the first indicator, wherein the bandwidth of the second PPDU is set to 80 MHz, 160 MHz or 320 MHz based on the second indicator.
 11. The method of claim 10, wherein the first PPDU includes a first Short Training Field (STF) and a first Long Training Field (LTF), wherein the second PPDU includes a second STF and a second LTF.
 12. The method of claim 11, wherein if the bandwidth of the first PPDU is 80 MHz, the first STF includes a HE-STF sequence for an 80 MHz band, and the first LTF includes a HE-LTF sequence for an 80 MHz band, wherein if the bandwidth of the first PPDU is 160 MHz, the first STF includes a HE-STF sequence for a 160 MHz band, and the first LTF includes a HE-LTF sequence for a 160 MHz band.
 13. The method of claim 11, wherein if the bandwidth of the second PPDU is 80 MHz, the second STF includes an EHT-STF sequence for an 80 MHz band, and the second LTF includes an EHT-LTF sequence for an 80 MHz band, wherein if the bandwidth of the second PPDU is 160 MHz, the second STF includes an EHT-STF sequence for a 160 MHz band, and the second LTF includes an EHT-LTF sequence for a 160 MHz band, wherein if the bandwidth of the second PPDU is 320 MHz, the second STF includes an EHT-STF sequence located in the secondary 160 MHz channel among an EHT-STF sequence for a 320 MHz band, and the second LTF includes an EHT-LTF sequence located in the secondary 160 MHz channel among an EHT-LTF sequences for a 320 MHz band. 14-16. (canceled) 